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

microsoft-todo-mcp-server

by vexxhost
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Delete checklist item

delete_checklist_item
Destructive

Remove a specific checklist item from a Microsoft To Do task by providing the list, task, and checklist item IDs.

Instructions

Delete a checklist item (subtask) from 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>",
      "checklist_item_id": "<checklist_item_id>"
    },
    "name": "delete_checklist_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
list_idYes
task_idYes
checklist_item_idYes

Output Schema

NameRequiredDescriptionDefault
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already provide destructiveHint: true, and the description does not add behavioral details beyond stating the action, but does not contradict annotations.

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?

Single sentence with no wasted words, efficiently conveys the core action.

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?

For a simple delete operation, the description is adequate but could benefit from parameter explanations and return value details, especially given the output schema exists.

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?

Input schema has 0% description coverage, and the description does not explain the three required parameters (list_id, task_id, checklist_item_id), failing to add meaning beyond the schema.

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 specific verb 'Delete' and resource 'checklist item (subtask)', and distinguishes from sibling tools like create_checklist_item 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 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, such as checking if the item exists or confirming destructive intent.

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