Skip to main content
Glama

Update board settings

kanbini_update_board

Updates a board by changing only specified fields: rename it, set or clear its home-card description or color, or pin it to the top of the picker.

Instructions

Patch a board. name renames it; description is the short blurb on the home picker (null clears it); color is the board accent shown on its home card and header tint (null clears it); pinned favourites it to the top of the home picker. Omit fields you do not want to change. id is the board id or its exact name. To archive a board use kanbini_archive_board. Colours: pass a palette name (red, orange, amber, yellow, lime, green, teal, cyan, sky, blue, indigo, purple, pink, rose) so it matches the app's swatch picker.

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>",
      "patch": "<patch>"
    },
    "name": "kanbini_update_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
patchYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.4/5.0
Behavior4/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 that null clears description and color, that omitted fields are untouched, and that `id` accepts either an id or an exact board name. It does not cover permission requirements, what a rename does to existing references, or what a successful patch returns.

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 verb is front-loaded and the field walkthrough is dense and purposeful, with clearing semantics inline. The trailing sentence repeating the full palette list largely duplicates the `color` property description already present in the schema, which is the one piece of redundancy.

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 mutation tool with a nested patch object, no annotations, and no output schema, the description covers field semantics, clearing behavior, partial-update rules, and id resolution. The remaining gap is response/error behavior, which is the only thing an agent might still want to know.

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 reported as 0%, so the description must supply meaning, and it does for every field: name=rename, description=home-picker blurb with null-clears, color=accent with null-clears and the palette constraint, pinned=favourite-to-top, id=id-or-exact-name. This is substantially more than the bare types in the schema 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?

"Patch a board" gives a specific verb and resource, and each sentence after it enumerates exactly what the patch can change (name, description, color, pinned). The final sentence explicitly routes archiving to kanbini_archive_board, so an agent can separate this from the destructive sibling tools without opening a 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?

"Omit fields you do not want to change" establishes partial-update semantics, and "To archive a board use kanbini_archive_board" gives an explicit alternative for the most confusable operation. It does not mention kanbini_delete_board, so the destructive boundary is only partly drawn.

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