Skip to main content
Glama

delete_task

DestructiveIdempotent

Borra una tarea: deja de verse en todas las listas y NO se puede recuperar desde estas herramientas.

Casi nunca es lo que se quiere: una tarea terminada se cierra con
complete_task y una que ya no va se cancela con `status: 'cancelled'` —
las dos quedan en el historial, que es de donde salen los informes. Borrar
es sólo para lo que se creó por error.

Fuera de Secondbrain: si la tarea está en ClickUp o Jira, la baja viaja allá (papelera de ClickUp, issue cerrado en Jira).

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_idYesID de la task
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo

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?

The annotations already flag destructiveHint=true and openWorldHint=true, but the description supplies the concrete consequences the flags cannot: irreversibility within these tools, removal from all lists, and propagation to connected systems (ClickUp trash, closed Jira issue). That is exactly the added context a destructive tool needs beyond a boolean hint.

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 blocks: what it does and its irreversibility, why you probably want something else, and the external-system side effect. Front-loaded and every sentence carries information; nothing is repeated from the annotations or schema.

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 two-parameter destructive tool with no output schema, the definition covers the effect, the alternatives, the irreversibility, and the cross-system propagation. An agent has everything it needs to decide whether to call it and what calling it will do.

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?

Schema description coverage is 100%, with both task_id and workspace_id documented in the schema itself, so the baseline is 3. The description adds no syntax, format, or resolution detail about either parameter (for example, whether task_id accepts a name or what happens if workspace_id is omitted on a multi-workspace token).

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?

"Borra una tarea" gives a specific verb and resource, and it immediately qualifies the effect: the task stops appearing in every list and cannot be recovered from these tools. That single sentence separates it from complete_task and from a status change without the agent needing to open any schema.

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 explicitly that this is almost never the wanted action, then names the two preferred alternatives (complete_task for a finished task, status 'cancelled' for an abandoned one) and the reason they are preferred (they stay in the history that reports are built from). It closes with the only legitimate use case: something created by mistake.

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