Skip to main content
Glama

KanbanMCP

Undo the last change to a card

undo
Destructive

Reverts the card's latest recorded change. Calling it again redoes the change.

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": {
      "cardId": "<cardId>"
    },
    "name": "undo"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardIdYesCard id, number (12) or key (WEB-12).
boardIdNoBoard id or slug.
personaNoThe persona to act as.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds genuinely new context beyond them: the call is a toggle, so a second invocation redoes the reverted change. It omits edge cases such as what happens when there is no recorded change to revert.

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, no filler, with the core action front-loaded and the non-obvious toggle behavior immediately after.

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

Completeness3/5

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

For a simple single-action tool with full schema coverage and annotations carrying the destructive/non-idempotent profile, the description is adequate but thin: it doesn't say what happens on failure (no change to undo) or whether the undo scope is per-user or per-card-global.

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%, so cardId, boardId, and persona are already documented in the schema. The description adds no syntax, scope, or format information beyond that, making the baseline 3 appropriate.

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?

States a specific verb and resource: 'Reverts the card's latest recorded change.' An agent immediately understands this is the inverse of a card mutation, though it never names or contrasts with siblings like update_card or resolve.

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?

The note that calling it again redoes the change implies toggle usage, but there is no explicit when-to-use versus alternatives (e.g., re-editing the card directly), no prerequisites, and no exclusions.

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