Skip to main content
Glama

Stop a card waiting on another

kanbini_remove_blocker

Remove the blocking link between two cards so one no longer waits on another. Identify cards by ID or card number with board ID; nonexistent links are ignored.

Instructions

Remove the link that makes card cardId wait on card blockerId. Removing a link that doesn't exist does nothing. Neither card changes otherwise. 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).

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_remove_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.1/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does well on the safety-critical points: it declares that a missing link is a no-op (idempotent, safe to retry) and that no other card state is mutated. It omits permission/authorization requirements and does not say whether the removal can be undone or what the call returns, which keeps it short of a 5.

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?

Four short sentences, each doing distinct work: core action, edge-case behavior, side-effect bound, then reference format. Front-loaded and free of filler, with only minor phrasing friction in "A card can be given by its id."

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

Completeness4/5

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

For a three-parameter mutation with no annotations and no output schema, the description covers action, idempotency, non-effects, and identifier formats adequately. The remaining gap is response shape and error/permission behavior, which nothing else in the definition supplies.

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 only 33%, and the description compensates by explaining that a card may be referenced either by raw id or by its on-card number (`#142`) in which case `boardId` is needed. That materially adds meaning beyond the schema, though it is slightly ambiguous whether the number-plus-`boardId` form applies to `blockerId` as well as `cardId`.

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 first sentence names a specific verb and resource pair: remove the blocking link between card `cardId` and card `blockerId`. It is unambiguous and immediately distinguishable from the inverse sibling `kanbini_add_blocker`, and the scope statement ("Neither card changes otherwise") prevents an agent from expecting broader card edits.

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 by the operation itself (you remove a blocker that was previously added), and the idempotency note helps the agent act without a pre-check. However, the description never explicitly names the alternative `kanbini_add_blocker` or states the condition that selects between them, so the routing guidance is inferential rather than explicit.

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