Skip to main content
Glama

Add a checklist to a card

kanbini_create_checklist

Create a checklist on a Kanbini card and add ordered items in one call, returning its id and boardId so you can add more checklist items later.

Instructions

Create a checklist on a card, with its items (texts, in order) in the same call. Returns { id, boardId }; add more later with kanbini_add_checklist_item. 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>",
      "name": "<name>"
    },
    "name": "kanbini_create_checklist"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields 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."
    • addedInput schema / properties / items
      Added value: +{
      +  "items": {
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "maxItems": 200,
      +  "type": "array"
      +}
  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.2/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. It does disclose the return shape ({ id, boardId }) and the items-ordering behavior, which is useful. It says nothing about failure modes (duplicate names, invalid card number), permission requirements, or limits on item count.

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 tight sentences, front-loaded with the create-plus-items capability, then the return value, then the addressing rules. Every clause carries information an agent needs; nothing is redundant with the title.

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 four-parameter creation tool with no output schema and no annotations, the description covers the return value, the extension path, and the non-obvious card-addressing convention. Remaining gaps (error conditions, uniqueness constraints) are modest but real.

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 25% (boardId alone), so the description must compensate, and it largely does: it explains that cardId accepts either an id or a card number like #142, that boardId is then required and accepts an id or exact board name, and that items are texts applied in order. Only the checklist `name` parameter and the 200-item cap are left to the schema, which is acceptable.

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 opens with a specific verb and resource ("Create a checklist on a card") and immediately scopes it as creating the checklist together with its items in one call. That scope detail is exactly what separates it from the sibling kanbini_add_checklist_item, which is named explicitly.

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 gives clear routing guidance: create the checklist with its items here, and use kanbini_add_checklist_item for later additions. It also explains the two addressing modes for a card (id vs. #number plus boardId). It does not address what to do if a checklist with that name already exists, or whether multiple checklists per card are allowed.

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