Skip to main content
Glama

rollback_task

DestructiveIdempotent

Reabre una tarea cerrada: vuelve a pending y BORRA completed_at.

Es el camino correcto para desmarcar algo, no update_task: sin limpiar la
fecha de cierre, la tarea vuelve al radar arrastrando el día en que se dio
por terminada y el historial de trabajo la sigue contando ahí.

Falla a propósito si la tarea no estaba cerrada.

Fuera de Secondbrain: si la tarea está en ClickUp o Jira, se reabre también allá.

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": "rollback_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesID numérico de la tarea
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.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true; the description adds real value on top by specifying that `completed_at` is erased and that the call deliberately errors on a non-closed task. It also discloses that the reopen propagates to ClickUp/Jira. It stays silent on secondary effects such as notifications to assignees or whether a history entry is written, so it falls short of a 5.

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?

The core effect is front-loaded in the first sentence, followed by rationale, failure mode, and cross-system scope in a logical order. The middle explanation about the radar and work history is slightly verbose but justifies the existence of the tool over update_task.

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 two-parameter mutation tool with no output schema, the definition covers state transition, the deleted field, error behavior, and external-system propagation. The only gap is what a successful call returns or how external-system failures surface, which an agent would want before invoking it.

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 coverage is 100%, so task_id and workspace_id are already documented in the schema and the baseline of 3 applies. The description adds no parameter-level meaning: it never explains that task_id may refer to an external ClickUp/Jira task despite describing cross-system behavior, nor does it clarify workspace_id resolution.

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?

States a specific verb + resource ("Reabre una tarea cerrada") plus the exact resulting state ("vuelve a `pending`") and the field it removes ("BORRA `completed_at`"). It also distinguishes itself from the sibling update_task in the same breath, so an agent can tell the two apart without opening either 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?

Explicitly names the alternative (update_task) as the wrong path and explains why using it leaves stale completion data. It also states when the tool will not work ("Falla a propósito si la tarea no estaba cerrada") and covers the non-Secondbrain case (ClickUp/Jira), giving both when-to-use and when-it-fails guidance.

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