Repository navigation
docs: fix README tool parameter names from snake_case to camelCase - #50
Merged
Merged
Conversation
Copilot
AI
changed the title
[WIP] Fix README documents to match camelCase tool parameters
docs: fix README tool parameter names from snake_case to camelCase
Jul 1, 2026
ml-aixolotl
marked this pull request as ready for review
July 1, 2026 08:25
ml-aixolotl
approved these changes
Jul 1, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the README’s “Available Tools” parameter documentation to match the MCP tool schemas’ camelCase parameter names, preventing caller errors caused by outdated snake_case docs.
Changes:
- Updated plan/bucket/task tool parameter names in README tables from snake_case to camelCase (e.g.,
plan_id→planId,task_id→taskId). - Documented previously missing
update_taskparameters (priority,appliedCategories). - Updated the
update_taskprose note to reference the correct camelCase detail-field parameter names.
| | `percentComplete` | integer | No | Completion percentage, 0–100 | | ||
| | `dueDateTime` | string | No | ISO 8601 due date | | ||
| | `bucketId` | string | No | ID of the bucket to move the task to | | ||
| | `priority` | integer | No | Priority 0 (urgent)–10 (low). Planner maps: 1=urgent, 3=important, 5=medium, 9=low | |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The README's "Available Tools" parameter tables documented snake_case names (e.g.
plan_id,task_id,checklist_items) while the actual MCP tool schemas expose camelCase (e.g.planId,taskId,checklistItems), causingmissing_argument/unexpected_keyword_argumenterrors for anyone calling tools by the documented names. The drift was introduced in PR #43 when parameters were aligned with Graph API field naming but docs were not updated.Changes
group_id→groupId,plan_id→planIdacrosslist_group_plans,create_plan,delete_plan,list_plan_categoriesplan_id→planId,bucket_id→bucketIdacrosslist_buckets,create_bucket,delete_bucketplan_id→planId,bucket_id→bucketId,task_id→taskId,start_date_time→startDateTime,due_date_time→dueDateTime,percent_complete→percentComplete,assign_user_ids→assignUserIds,unassign_user_ids→unassignUserIds,assignee_priority→assigneePriority,preview_type→previewType,checklist_items→checklistItems,etag_details→etagDetailsupdate_taskparams:priorityandappliedCategorieswere implemented but undocumentedupdate_taskwhich also referenced the old snake_case names