Skip to main content
Glama

todo_delete_task

Delete a task by list ID and task ID from Microsoft To Do or Microsoft Planner to remove completed or obsolete items and keep task lists current.

Instructions

Delete a task.

Input Schema

NameRequiredDescriptionDefault
list_idYes
task_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about irreversibility, whether checklist items/subtasks cascade-delete, or required permissions. The only signal is the implicit destructiveness of the word "delete".

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

Conciseness2/5

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

At four words there is no waste, but this is under-specification rather than conciseness. Nothing is front-loaded because there is nothing to front-load.

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?

An output schema exists, so return values need no explanation, but for a destructive two-parameter mutation with no annotations this description omits the essentials: what gets destroyed, cascade behavior, and parameter meaning. It is not complete enough to call safely.

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?

Schema description coverage is 0% for both required parameters (list_id, task_id), and the description does not mention either one. There is nothing explaining that a task must be identified jointly by its list and its id, which is the key invocation detail.

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

Purpose3/5

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

"Delete a task" gives a clear verb and resource, but it is almost a verbatim restatement of the tool name todo_delete_task and draws no distinction from siblings like todo_delete_list or todo_delete_checklist_item. An agent knows the general operation but nothing about its scope or effect.

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 on when to use this versus deleting a whole list, completing a task, or removing a checklist item. There are no preconditions, no mention of whether the task must exist, and no exclusions.

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