Skip to main content
Glama

Delete task

delete_task
DestructiveIdempotent

Delete one task. ALWAYS ask the user to confirm before calling this (name the task and its day), unless they explicitly asked to delete that exact task. On a repeating occurrence only that day is removed (use stop_repeating_task to end the series). To tick a task off, use complete_task instead. A deletion can be reverted with undo_last_change.

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": {
      "id": "<id>"
    },
    "name": "delete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTask id from get_week, list_tasks or search_tasks (also "repeat_…" ids of repeating occurrences).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the destructive and idempotent annotations, the description adds important behavioral context: user confirmation is required, only one occurrence of a repeating task is removed, and the deletion can be reverted with undo_last_change.

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?

The description is compact and front-loaded with the main action. Each sentence adds useful guidance, and there is no unnecessary wording.

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

Completeness5/5

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

For a destructive mutation with one parameter and no output schema, the description covers the critical operational details: confirmation, repeating-occurrence behavior, alternatives, and reversibility.

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

Parameters3/5

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

With 100% schema description coverage, the schema already documents the single id parameter and its valid sources. The description does not add further syntax or format details beyond what the schema provides.

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 states a specific verb and resource: "Delete one task." It also explicitly distinguishes this from deleting multiple tasks by specifying "one," and routes other actions to complete_task and stop_repeating_task.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance, including a mandatory confirmation instruction before calling, an exception for explicit user requests, and clear alternatives for completing or stopping repeating tasks.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources