microsoft-todo-mcp-server

Overview Schema Source Related Servers Discussions Admin

Update task

update_task

Idempotent

Update selected fields of a task in Microsoft To Do—title, body, due date, importance, or status—without altering other properties.

Instructions

Update a task in a Microsoft To Do task list. Only provided fields are updated.

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>"
    },
    "name": "update_task"
  }
}

Input Schema

Name	Required	Description	Default
`body`	No
`title`	No
`status`	No
`list_id`	Yes
`task_id`	Yes
`due_date`	No
`importance`	No

Output Schema

Name	Required	Description	Default
`id`	Yes
`title`	Yes
`status`	Yes
`due_date`	Yes
`created_at`	Yes
`importance`	Yes
`body_content`	Yes
`completed_at`	Yes
`body_content_type`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 14, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds that only provided fields are updated, which is critical behavioral detail beyond annotations—it clarifies that omitted fields remain unchanged and that the operation is a partial update. This aligns with the idempotency hint.

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

Conciseness5/5

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

The description is a single sentence, concise and front-loaded with the action. It contains no fluff and directly states the core behavior.

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

Completeness4/5

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

Given the complexity (7 parameters, 0% schema coverage) and presence of an output schema, the description covers the essential partial update behavior. However, it lacks parameter-level guidance, which the output schema may partially address. The description is adequate but not exhaustive.

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?

Schema description coverage is 0%, so the description must compensate but does not. It only states that provided fields are updated, without listing or explaining any of the 7 parameters (e.g., title, body, status, due_date, importance). The agent must infer parameter purposes solely from their names and types.

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 'a task in a Microsoft To Do task list'. It distinguishes from siblings like 'complete_task' or 'delete_task' by specifying that only provided fields are updated, making partial updates explicit.

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 indicates that only provided fields are updated, implying it is for modifying specific task attributes. However, it does not provide explicit guidance on when to use this tool versus alternatives (e.g., 'complete_task' for status changes, 'create_task' for new tasks), nor does it mention any exclusions or prerequisites.

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

Deploy Server