Skip to main content
Glama

Delete a task

delete_task
DestructiveIdempotent

Delete a task for good, with its history (ticker, abortions). Cannot be undone: confirm with the user first.

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

Input Schema

NameRequiredDescriptionDefault
task_idYesThe task's id (from list_tasks, todays_tasks or a loop's tasks).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety bar is partly met by structured data. The description earns credit for adding behavior that annotations cannot express: the delete cascades to associated history (ticker, abortions) and is irreversible. It omits permissions requirements and any return/response detail.

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

Conciseness4/5

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

A single tight sentence with the destructive scope front-loaded and the confirmation warning placed last as the immediate caveat. Slight deduction for the ambiguous term "abortions", which is unexplained and may read as unrelated to task deletion.

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 one-parameter destructive tool with no output schema and annotations carrying the safety profile, the description supplies exactly the missing pieces: cascade scope, irreversibility, and a user-confirmation requirement. Nothing an agent needs in order to call this safely is absent.

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 one parameter at 100% schema description coverage, the schema already explains that task_id comes from list_tasks, todays_tasks, or a loop's tasks. The description adds no further meaning about the identifier, so the baseline of 3 applies.

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?

States a specific verb and resource ("Delete a task") and adds scope details that the name alone would not convey: the deletion is permanent and cascades to the task's history. It does not, however, distinguish itself from siblings like delete_loop or abort_task, which are the nearest ambiguous alternatives for an agent.

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

Usage Guidelines3/5

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

The description gives one clear precondition — "confirm with the user first" — which is genuinely actionable. It stops short of saying when to choose permanent deletion over aborting or dequeueing a task, so the agent must infer the boundary from the word "for good".

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