Skip to main content
Glama
Sign In
microsoft-todo-mcp-server

microsoft-todo-mcp-server

by vexxhost
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Update checklist item

update_checklist_item
Idempotent

Update a checklist item's name or completion status in Microsoft To Do. Modify display name or toggle checked state.

Instructions

Update a checklist item (subtask) of a Microsoft To Do task. Use is_checked to check/uncheck.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "list_id": "<list_id>",
      "task_id": "<task_id>",
      "checklist_item_id": "<checklist_item_id>"
    },
    "name": "update_checklist_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
list_idYes
task_idYes
is_checkedNo
display_nameNo
checklist_item_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
is_checkedYes
display_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate idempotentHint=true and non-destructive; the description adds minimal behavioral context beyond the 'check/uncheck' hint, failing to disclose auth needs, error conditions, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no fluff, though it could benefit from slightly more detail without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple and has an output schema, but the description omits prerequisites, required fields context, and error handling, making it adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, the description only clarifies 'is_checked' for check/uncheck, leaving list_id, task_id, checklist_item_id, and display_name unexplained, which is insufficient compensation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'update' and the resource 'checklist item (subtask)' within Microsoft To Do, distinguishing it from sibling creation, deletion, and listing tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for modifying existing items and highlights checking/unchecking via is_checked, but lacks explicit guidance on when to use this tool versus alternatives like complete_task.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools