Skip to main content
Glama

KanbanMCP

Change a label

label
DestructiveIdempotent

Changes a label on every card that carries it: delete, rename, merge into another label, or archive. Call it without confirm first. The answer says how many cards carry the label, and nothing changes. Change a label only when a person or your task asks you to. Never to tidy up. To apply, pass confirm true and a short reason.

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": {
      "action": "<action>",
      "name": "<name>"
    },
    "name": "label"
  }
}

Input Schema

NameRequiredDescriptionDefault
intoNoMerge target, or the new name for rename.
nameYesThe label.
actionYesWhat to do to the label.
reasonNoWhy, in one line. Needed with confirm.
boardIdNoBoard id or slug.
confirmNoApply it. Left out, nothing changes.
personaNoThe persona to act as.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Adds traits the annotations cannot express: omitting confirm is a no-op dry run, the response reports how many cards carry the label, and applying requires a reason. Annotations already flag destructive/idempotent, and the description extends rather than repeats them.

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?

Compact and front-loaded: purpose first, then the dry-run protocol, then the guardrail. Slight redundancy between 'Call it without confirm first' and 'To apply, pass confirm true', but every sentence conveys real instruction.

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?

No output schema exists, and the description compensates by describing the return ('how many cards carry the label'), the default no-op behavior, and the confirmation requirement. Nothing an agent needs to invoke this destructive tool safely is missing.

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 100%, so the baseline is 3. The description adds beyond that by tying confirm and reason together as a required pair for execution and implying confirm's absence means no-op, plus 'into' semantics for merge vs rename.

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 and resource ('Changes a label') plus scope ('on every card that carries it') and enumerates the four supported operations matching the action enum. This distinguishes it from update_card, which edits a card's own fields rather than mutating a label globally.

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?

Gives an explicit two-phase protocol ('Call it without confirm first' / 'To apply, pass confirm true and a short reason') and a clear when-not ('only when a person or your task asks you to. Never to tidy up'). An agent has no ambiguity about when this tool should fire.

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