Skip to main content
Glama

Coline

Undo a change to a task

undo_task_change
Destructive

Sets a field back to what it was before one change in a task's history, while that field hasn't changed since. mode bring_back restores an earlier description even after later edits.

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": {
      "workspace": "<workspace>",
      "taskboardId": "<taskboardId>",
      "eventId": "<eventId>"
    },
    "name": "undo_task_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoundo
eventIdYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
taskboardIdYes

Output Schema

NameRequiredDescriptionDefault
taskIdYes
undoneYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already disclose that this is destructive and non-idempotent. The description adds useful safety context by noting the unchanged-since condition and the special 'bring_back' behavior, but it does not elaborate on permissions, irreversibility, or exactly what is overwritten.

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 sentences with no filler: the core operation is front-loaded, and the mode exception follows immediately. The structure makes the key condition easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description gives a usable mental model of the undo behavior and the 'bring_back' exception, and an output schema covers return values. However, for a four-parameter destructive tool with low schema coverage, it omits essential meaning for required parameters such as 'taskboardId' and 'eventId'.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%, so the description must compensate. It explains 'mode' partially and implies 'eventId' refers to a history change, but it leaves 'taskboardId' and the precise role/format of 'eventId' undocumented.

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/resource pair: 'Sets a field back' within 'a task's history.' It clearly frames the tool as an undo operation and adds the special 'bring_back' mode, though it does not explicitly name sibling alternatives.

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?

It gives the core precondition for undo: the field must not have changed since the target change. It also explains when 'bring_back' applies, but it does not explicitly compare this tool with history-reading or generic task-update alternatives.

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