Skip to main content
Glama

delete_task

Destructive

Delete a task for good. Prefer update_task with status done or archived unless the user asked to delete.

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
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is known from structured data, and "for good" largely restates it. The description adds useful steering toward a reversible alternative, but says nothing about whether deletion cascades to related records, whether it is recoverable via any other means, or what happens when the id is unknown.

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?

Two short sentences, both front-loaded with the consequential information: the destructive effect first, then the safer default. There is no filler or hedging that an agent must parse around.

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 one-parameter destructive tool with sufficient annotations and no output schema, the description covers purpose, irreversibility, and the preferred alternative. The only meaningful omission is downstream effects of deletion, which is a minor gap given how simple the call is.

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?

There is a single required parameter, id, at 0% schema description coverage, and the description says nothing about it — not its format, not which identifier it is (task id vs. external source id), not what an invalid id does. With only one parameter the gap is small, but the description adds no meaning over the bare 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 gives a specific verb and resource ("Delete a task") and adds the permanence qualifier "for good", making the effect unambiguous. It is trivially distinguishable from the sibling mutation tool update_task, which it explicitly names.

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 states the preferred alternative (update_task with status done or archived) and the exact condition under which this tool is instead correct ("unless the user asked to delete"). That is an explicit when-to-use and when-not-to-use rule rather than an inference.

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