Skip to main content
Glama

Get Kanbini board

kanbini_get_board

Retrieve one Kanbini board with its labels and every list's cards, so you can see card numbers, titles, due dates, priorities and blockers. Filter or page longer lists with other tools.

Instructions

Return one board: its labels, and every list with its cards. By default (detail: "summary") each card is one short line: number (the #N shown on the card, counted per board), title, and only what applies: completed, due (YYYY-MM-DD), priority, labels (names), checklist ("ticked/total"), description: true when it has one, comments / attachments counts, blocked (waiting on an open card), repeat. A list shows its first cardsPerList cards (default 50, in board order); a longer one says how many it left out in moreCards, and kanbini_get_list_cards filters or pages through them. Cards are named by number: pass #142 with this boardId to any tool that takes a card, and use kanbini_get_card for its description, checklists, comments and history. For one list, filtered (open / done, label, priority, due, text) or paged, use kanbini_get_list_cards. detail: "full" returns every card with all of its content, which is very large on a big board: avoid it. Archived cards are left out; archived lists show closed: true with no cards (kanbini_list_archived lists both). A list's visibleCardLimit / cardDensity and a card's collapsed are display settings only: every card is still returned. boardId is the id or exact name; omitted, the first board. Returns null if it matches nothing. When the desktop app is closed, falls back to the last on-disk export.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kanbini_get_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNo
boardIdNo
cardsPerListNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.17.0
    • addedInput schema / properties / cardsPerList
      Added value: +{
      +  "exclusiveMinimum": 0,
      +  "maximum": 1000,
      +  "type": "integer"
      +}
    • addedInput schema / properties / detail
      Added value: +{
      +  "enum": [
      +    "summary",
      +    "full"
      +  ],
      +  "type": "string"
      +}
  2. First observedv0.13.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses the default summary shape, the cardsPerList default of 50 and truncation via moreCards, the exclusion of archived cards, the closed-list behavior, the null return when nothing matches, and the fallback to the last on-disk export when the desktop app is closed. These are exactly the non-obvious behaviors an agent needs before calling a read tool.

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?

The content is dense and front-loaded with the core return shape, but it is delivered as one long paragraph mixing return fields, pagination, display-setting caveats, and offline fallback. Every sentence is informative, yet clearer segmentation would make it easier to scan.

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?

There is no output schema, so the description must explain return values — and it details card fields, list truncation, and the archived-list case thoroughly. Combined with its explanation of all three parameters and the offline fallback, nothing material is missing for a read tool of this complexity.

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 0%, so the description must supply all parameter meaning — and it does. It explains boardId accepts an id or exact name and defaults to the first board, detail distinguishes summary from the very large full mode, and cardsPerList is the per-list card cap defaulting to 50 in board order.

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?

Opens with a specific verb and resource — 'Return one board: its labels, and every list with its cards' — and immediately distinguishes itself from kanbini_get_list_cards and kanbini_get_card. An agent can identify the tool's exact scope without opening the schema.

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?

Explicitly routes the agent: use kanbini_get_list_cards for one list, filtered results, or paging; use kanbini_get_card for descriptions, checklists, comments, and history; use kanbini_list_archived for archived lists. It also warns agents to avoid detail: 'full' on large boards, which is a clear when-not-to-use instruction.

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