Skip to main content
Glama

Create a board

kanbini_create_board

Create a new empty Kanban board with a required title and optional description, returning its board ID so you can add lists and cards next.

Instructions

Create a new empty board (no lists, no cards). name is the required board title; description is an optional short blurb shown on the home picker. Returns { id, boardId } - both equal the new board's id. Add columns next with kanbini_create_list, then cards with kanbini_create_card (or all of it in one kanbini_batch).

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

Input Schema

NameRequiredDescriptionDefault
nameYes
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.6/5.0
Behavior4/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 disclose key behavior: the board is created empty, and the response shape is { id, boardId } with both equal to the new board's id. It omits failure modes such as duplicate names or permission requirements, keeping it from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly packed sentences: what is created, what the parameters mean, what is returned, and what to do next. No filler, and the core purpose is front-loaded.

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?

No output schema exists, but the description explains the return shape itself, and the two-parameter create tool is fully covered by the parameter prose plus follow-up routing to create_list/create_card/batch. Nothing an agent needs to invoke it correctly is missing.

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 compensate, and it does: `name` is identified as the required board title and `description` as an optional short blurb shown on the home picker — meaning the schema does not 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 ("Create a new empty board") and immediately scopes it with "(no lists, no cards)", which distinguishes this creation tool from siblings like kanbini_update_board, kanbini_copy_card, or kanbini_batch.

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 sequencing guidance: add columns with kanbini_create_list, then cards with kanbini_create_card, or do it all in kanbini_batch. It does not state explicit exclusions (e.g., when to prefer batch over individual calls beyond the parenthetical), so it falls short of a 5.

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