Skip to main content
Glama

Get Kanbini card

kanbini_get_card

Retrieves a Kanbini card by ID or board-specific number, returning its details, checklists, comments, attachments, activity, and blocking links so you can inspect or act on the right card.

Instructions

Return one Kanbini card by id OR by its number - #142 or 142, the short #N the app shows on the card, which is how the user refers to cards. Numbers are counted per board, so a number needs its boardId (the id or name of the board the user means; without one this errors and lists the boards that have that number). Numbers handed out before they were per board are gone: look a card up again rather than trusting an old number. boardId is ignored for an id. Includes its id, number and boardId (keep the number and board together), title, description, priority (low/medium/high/urgent or null), checklists (with item ids), comments, attachments, recent activity feed, and its "waiting on" links: blockedBy (cards it waits on) and blocking (cards waiting on it), each with title, completed, archived, board, and list. A card is blocked while any blockedBy card is neither completed nor archived. Works for archived cards too (see kanbini_list_archived). Returns null if the id, or the number on that board, does not exist. When the desktop app is closed, falls back to the last on-disk export.

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": {
      "id": "<id>"
    },
    "name": "kanbini_get_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
boardIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does well: it discloses the error path (without boardId a number lookup errors and lists candidate boards), null on non-existent id/number, the on-disk export fallback when the desktop app is closed, and the blockedBy/blocking blocking rule. The gap is that it never says this is a read-only tool, so an agent gets no explicit safety statement—only inference from 'Return'—which holds it below a 4.

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?

Front-loaded with the core fact (lookup by id or number) and organized around the number-vs-id decision, so the reader hits the important constraint first. It runs long and packs multiple parenthetical asides into single sentences, but since there is no output schema the return-field enumeration earns most of its space.

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 two-parameter lookup with no annotations and no output schema, the description covers everything an agent needs: input forms, required boardId for numbers, error and null outcomes, archived-card coverage, the offline export fallback, and the full return shape including blocker links and the blocking rule.

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 0%, so the description must define both parameters, and it does: id accepts either a raw id or the '#142'/'142' short number, and boardId accepts a board id or name, is required for number lookups, and is ignored for id lookups. The per-board numbering rule and the error behavior add genuine meaning the bare string schema cannot convey.

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 ('Return one Kanbini card') and immediately clarifies the two lookup modes: by id or by the short #N number the app shows. That dual-mode framing plus the note that archived cards resolve here too (pointing at kanbini_list_archived) lets an agent distinguish it from sibling tools without opening any schema.

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?

Gives clear conditional guidance: numbers are per board so a number requires boardId, boardId is ignored when using an id, and pre-per-board numbers are invalid so cards must be re-looked-up. It does not name kanbini_search_cards as the alternative when the agent only has text to match, which keeps it from a 5.

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