Skip to main content
Glama

delete

Move a task to the 30-day trash or remove an empty project; restore a trashed task by ID.

Instructions

Delete a task (kept in the trash 30 days) or an empty project. Confirm first. restore= brings a deleted task back.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNo
projectNopath or id
restoreNoid of a deleted task

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: deletion is soft (30-day trash retention), user confirmation is required, project deletion is gated on emptiness, and restore re-activates a deleted task. Gaps remain around permissions and what happens after the 30 days or when both task and project are passed, but the core behavioral profile is disclosed.

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?

Three short, front-loaded sentences with no filler; the destructive action and its safeguard lead. The telegraphic "restore=" phrasing is slightly choppy but costs nothing in clarity.

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 three-optional-parameter mutation tool with no annotations and no output schema, the description covers retention, confirmation, eligibility constraints, and the restore mode. It does not clarify mutual exclusivity of task/project or the result of the call, minor gaps for a tool this simple.

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 67%, and the description compensates further: it explains that restore takes the id of a deleted task and brings it back, and that the project target must be empty. Only the bare `task` parameter is left to the schema alone, which is reasonable for an integer id.

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 uses a specific verb with two clearly enumerated targets: deleting a task or deleting an empty project. It also discloses a secondary mode (restore=) so an agent knows this tool is not purely destructive. It doesn't name a sibling such as save_task as the counterpart, but the resource and scope are unambiguous.

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?

"Confirm first" is an explicit precondition the agent must satisfy before invoking, and "empty project" implicitly excludes non-empty projects. The restore sentence points to the recovery path for deleted tasks. Missing is an explicit statement of what to use for non-empty project removal or how restore interacts with the delete parameters.

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