Skip to main content
Glama

Delete To Do Task

delete_todo_task
Destructive

Permanently deletes a Microsoft To Do task; deleting a repeating task requires force:true and ends the entire series.

Instructions

Delete a To Do task. There is no API to restore it, so treat it as permanent. Deleting a repeating task ends the whole series and needs force: true.

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": "delete_todo_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoRequired to delete a repeating task, which ends the whole series rather than one occurrence. To stop it repeating but keep the task, use clear_recurrence on update_todo_task instead.
list_idYesTo Do list ID
task_idYesTask ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuinely new context beyond that: irreversibility ('no API to restore it') and the series-wide side effect on repeating tasks. It does not cover permission requirements, but the key destructive semantics are disclosed.

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?

Three short sentences, with the action and the permanent-deletion warning front-loaded before the edge case. No filler, no restatement of the title, and every sentence carries decision-relevant information.

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?

For a destructive three-parameter tool with no output schema, the description supplies the irreversibility warning and the recurring-task caveat, which are the main things an agent needs to act safely. It is slightly incomplete on whether special permissions are required and on what a successful deletion returns, but annotations and schema cover most of the remaining ground.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description earns above that by explaining the behavioral meaning of force (series termination rather than single-occurrence deletion). list_id and task_id are left entirely to the schema, which is acceptable given full coverage.

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

Purpose4/5

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

The description opens with a precise verb+resource ('Delete a To Do task') that is unambiguous and clearly separable from siblings such as delete_todo_list or set_todo_task_state. It stops short of explicitly naming sibling alternatives in the description body, so it does not quite reach the top tier.

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

Usage Guidelines4/5

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

It gives a clear condition for the special case ('Deleting a repeating task ends the whole series and needs force: true') and warns the caller to treat the action as permanent. It does not explicitly tell the agent when to prefer an alternative, though the schema's force description points to clear_recurrence on update_todo_task.

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