MCP for Microsoft To Do

create_checklist_item

Add a checklist sub-item to a Microsoft To Do task. Specify the parent list, task, and the name of the new sub-item.

Instructions

Add a sub-item (checklist) to a task.

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

Input Schema

Name	Required	Description
`list_id`	Yes
`task_id`	Yes
`display_name`	Yes
`is_checked`	No
`verbose`	No	If true: returns full JSON. Otherwise: compact text format (default, saves tokens).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1May 5, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already indicate this is not read-only, not destructive, and not idempotent. The description adds no extra behavioral context (e.g., does creation affect task state, any side effects). Adequate but minimal.

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 wasted words. However, it is somewhat under-specified, barely above a tautology.

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

Completeness2/5

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

With no output schema and 5 parameters (3 required), the description is too sparse. It does not clarify the return format beyond the verbose parameter hint, nor does it explain ordering, error conditions, or relationship to the parent task.

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 only 20% (just verbose). The description does not elaborate on parameters like list_id, task_id, display_name, or is_checked, failing to add meaning beyond the schema for the majority of parameters.

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 'Add' and the resource 'a sub-item (checklist) to a task,' explicitly differentiating it from siblings like create_task and update_checklist_item.

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 adding a checklist item but provides no guidance on when to use this tool versus alternatives like delete_checklist_item or batch creation tools. No explicit context or exclusions are given.

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