Skip to main content
Glama

Archive or restore a card

kanbini_archive_card

Archive or restore a card to hide it from the board, search, and counts while keeping its list, position, checklists, comments, and attachments intact. Restoring returns it exactly where it was.

Instructions

Archive (archived: true) or restore (archived: false) a card. An archived card disappears from the board, search, and card counts but keeps its list, position, checklists, comments, and attachments, so restoring puts it back exactly where it was. Tell the user the card was archived rather than deleted: they can see and restore it in the app from the board's pencil menu > Archived..., and kanbini_list_archived finds it too. Prefer this over kanbini_delete_card when the user wants a card "out of the way". 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": {
      "id": "<id>",
      "archived": "<archived>"
    },
    "name": "kanbini_archive_card"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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."
  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.5/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 most of it: it discloses what disappears (board, search, card counts), what is preserved (list, position, checklists, comments, attachments), and that restore is positionally exact. It leaves out permissions requirements, idempotency on repeated archive calls, and what the call 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?

Front-loaded with the action and the flag mapping, then consequences, then alternatives, then parameter forms — a sensible order with no filler sentences. It is a dense single paragraph, and the user-facing messaging instruction could arguably be split out, but nothing is redundant.

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 three-parameter toggle with no output schema, the description covers action, side effects, recovery, sibling choice, and identifier formats — enough to call it correctly. The only real omission is what the tool returns and whether re-archiving an archived card errors.

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 33%, and the description compensates: it defines the semantics of the archived boolean in both directions and explains that id may be a literal id or a card number like #142, which requires boardId. The boardId parameter itself is already documented in the schema, so no credit is taken for it.

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 pair (archive/restore) on a specific resource (card) and immediately ties each behavior to the boolean value. It also names the siblings it must not be confused with (kanbini_delete_card, kanbini_list_archived), so an agent can disambiguate without opening other schemas.

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?

Gives an explicit routing rule: 'Prefer this over kanbini_delete_card when the user wants a card "out of the way".' It also supplies the recovery path (board pencil menu > Archived..., kanbini_list_archived) so the agent can reassure the user, and clarifies the restore direction via archived: false.

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