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

microsoft-todo-mcp-server

by vexxhost
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Create checklist item

create_checklist_item

Add a subtask to an existing Microsoft To Do task by providing the list, task, and checklist item name.

Instructions

Add a checklist item (subtask) to a Microsoft To Do 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

NameRequiredDescriptionDefault
list_idYes
task_idYes
display_nameYes

Output Schema

NameRequiredDescriptionDefault
idYes
is_checkedYes
display_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already indicate mutation (readOnlyHint=false). The description adds no additional behavioral traits beyond the annotation, such as effects on existing items, idempotency, or error conditions. With no annotations for safety, the description is insufficient.

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

Conciseness3/5

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

The description is very concise—one sentence. While it avoids verbosity, it omits necessary details, making it more under-specified than efficiently concise.

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?

Despite having an output schema, the description does not mention returning anything. The tool has 3 required parameters but no parameter explanations, leaving the overall context incomplete for an agent to use reliably.

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

Parameters1/5

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

The description provides no information about parameters. With 0% schema coverage, the agent must infer meaning from names alone (list_id, task_id, display_name), which is insufficient for correct invocation.

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 action ('Add'), the resource ('checklist item/subtask'), and the parent ('Microsoft To Do task'). It effectively distinguishes from siblings like create_task (creates a task) and list_checklist_items (lists items).

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., task must exist) or when not to use it, leaving the agent with no usage context.

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