Skip to main content
Glama

Mark a card as waiting on another

kanbini_add_blocker

Records that a card is blocked by another card, so it shows as blocked until the blocker is completed or archived. Adds a cross-board dependency link and rejects loops.

Instructions

Record that card cardId waits on card blockerId (a "blocked by" link). The card shows as blocked in the app until the blocker is completed or archived. The two cards may be on different boards. Adding a link that already exists does nothing. Rejected when both are the same card, or when blockerId already waits on cardId directly or through other cards (that would make a loop). A card's links are in the blockedBy and blocking arrays of kanbini_get_card. The user can undo in the app. A card can be given by its id, or by its number (#142, as shown on the card) with boardId (the id or name of the board it is on). Two numbers must both be on that board; for a blocker on another board, use its id.

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>",
      "blockerId": "<blockerId>"
    },
    "name": "kanbini_add_blocker"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardIdYes
boardIdNoThe board's id or exact name. Needed when you name a card by number (#142) or a list / label by name.
blockerIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.17.0
    • changedInput schema / properties / boardId / description
      Previous value: -"Only when a card is given by number (#142): the board it is on"New value: +"The board's id or exact name. Needed when you name a card by number (#142) or a list / label by name."
  2. Changed1 schema field changedv0.15.0
    • addedInput schema / properties / boardId
      Added value: +{
      +  "description": "Only when a card is given by number (#142): the board it is on",
      +  "type": "string"
      +}
  3. First observedv0.13.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well. It discloses idempotency for existing links, cycle rejection, cross-board applicability, app display behavior, undo availability, and where links can be inspected via `kanbini_get_card`.

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?

The description is long but dense and front-loaded with the core action and constraints. Every sentence conveys operational meaning: display effect, idempotency, rejection rules, cross-board behavior, lookup location, undo, and reference syntax.

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 three-parameter mutation tool with no output schema and no annotations, the definition is complete. It covers reference syntax, constraints, rejection cases, side effects, and inspection path, leaving no significant operational gaps.

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

Parameters5/5

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

Schema description coverage is only 33%, but the description compensates strongly. It explains the meaning of `cardId` and `blockerId`, how `boardId` is required for numeric card references, and the constraint that two card numbers must be on the same board.

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?

The description states a specific action and resource: record that card `cardId` waits on card `blockerId`, a 'blocked by' link. It clearly distinguishes this from removal and general card updates by explaining the resulting app-visible blocked state.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains when the operation is rejected: same card, duplicate links, or cycles created directly or indirectly. It also explains how to reference cards by id or number with `boardId`. It does not explicitly name `kanbini_remove_blocker` as the alternative for undoing, but the guidance is otherwise clear and actionable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.