Skip to main content
Glama

Archive or restore a board

kanbini_archive_board

Archive or restore a Kanbini board by ID or exact name. Archiving hides it from the home picker and removes its cards from search without deleting anything.

Instructions

Archive (archived: true) or restore (archived: false) a board. An archived board is hidden from the home picker (the user can still reach it with "Show archived") and its cards drop out of search. Nothing is deleted. kanbini_list_boards still returns archived boards, flagged archived: true. id is the board id or its exact name.

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>",
      "archived": "<archived>"
    },
    "name": "kanbini_archive_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
archivedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.6/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: it discloses visibility effects (hidden from home picker, recoverable via 'Show archived'), the downstream side effect that cards drop out of search, and the reversibility guarantee that nothing is deleted. It also preempts the false negative that a subsequent list_boards call might be treated as stale by noting archived boards are still returned and flagged.

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?

Front-loads the action and mode mapping, then layers the consequences, then the identifier semantics. Three sentences with no redundancy or filler.

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 two-parameter reversible mutation with no output schema, this covers nearly everything an agent needs. Minor omission: what becomes of the board's lists and comments (as opposed to cards' search visibility) is not stated.

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% and the description compensates fully: 'archived' is given the true/false meaning of archive vs restore, and 'id' is documented as accepting either a board id or its exact name. Only the ambiguity of what happens with duplicate names is left unaddressed.

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?

Names a specific verb pair (archive/restore) and the exact resource (a board), with the state value in parentheses. An agent can tell this apart from delete_board, archive_card, and archive_list 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?

The archived:true/false mapping makes the two modes explicit and 'Nothing is deleted' implicitly steers the agent away from delete_board when it only wants to hide a board. A one-line contrast naming the destructive alternative is the only missing piece.

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