Skip to main content
Glama

KanbanMCP

Link or unlink two cards

link
DestructiveIdempotent

Makes one card the blocking parent of another. The child waits until the parent reaches Done. Pass remove true to take the link away again.

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": {
      "parentId": "<parentId>",
      "childId": "<childId>"
    },
    "name": "link"
  }
}

Input Schema

NameRequiredDescriptionDefault
removeNoTrue removes the link. Left out, it adds one.
boardIdNoBoard id or slug.
childIdYesCard id, number (12) or key (WEB-12).
personaNoThe persona to act as.
parentIdYesCard id, number (12) or key (WEB-12).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond them: the parent/child gating semantics ('the child waits until the parent reaches Done') and the fact that the destructive path is opt-in via remove=true, which is the key detail for avoiding an unintended unlink.

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?

Three short sentences, front-loaded with the core effect and then the gating rule and the removal flag; nothing is padded. The remove sentence duplicates the schema's own wording, a minor redundancy rather than a real waste.

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 5-parameter, no-output-schema tool, the description covers the add path, the remove path, and the behavioral consequence of the link. Board/persona parameters are self-describing in the schema, and annotations carry the idempotency and destructiveness profile, so an agent has what it needs to invoke this correctly.

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, and the schema only documents parameter formats ('Card id, number (12) or key (WEB-12)'). The description adds directional role semantics the schema lacks: which card is the blocking parent and which is the waiting child, which is essential to passing parentId/childId in the right order. The remove explanation largely restates the schema text, so it is not a clean 5.

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 states a concrete verb and effect: it makes one card the blocking parent of another, with the child gated on the parent reaching Done. That is far more specific than the bare name 'link' and lets an agent understand the relationship being created. It does not, however, distinguish itself from the similarly-named sibling 'block', which an agent could easily confuse with this tool.

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?

Usage is implied rather than stated: the dependency semantics ('the child waits until the parent reaches Done') tell the agent when this tool is the right one, and the description explains that passing remove true reverses it. There is no explicit when-not guidance and no routing away from overlapping siblings such as 'block' or 'move_card'.

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