Kaiku

Archive issues

archive_issues

Destructive

Archive issues — put finished work on the shelf so boards and searches show what is still live. Nothing is deleted: an archived issue keeps its key, history and comments, search_issues finds it with archived in (true, false), and unarchive_issues brings it back. Only issues in a done status may be archived, exactly as on the board; any other is refused and named with the state it stands in ("not in a done status: AN-7"), while the rest of the list is archived. Takes a full member of each issue's project; a paused or archived project refuses every write.

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

Input Schema

Name	Required	Description	Default
`keys`	Yes	Issue keys, comma-separated: 'AN-1, AN-2, AN-3'.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations: clarifies that 'destructive' archiving deletes nothing, that key/history/comments persist, and that the action is reversible. It also discloses permission requirements ('takes a full member of each issue's project'), the paused/archived project refusal, and the partial-success semantics with an actual error string ('not in a done status: AN-7'). This is exactly the context annotations cannot carry.

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?

Effect is front-loaded in the first clause, then constraints and recovery follow in a logical order. The paragraph is dense with three distinct ideas (reversibility, status gating, permissions) but nearly every clause carries decision-relevant information; the inline error example is slightly verbose but earns its place.

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?

For a single-parameter mutation tool with no output schema, the description covers reversibility, failure mode, error message shape, permission model, and project-state preconditions — everything an agent needs to predict the outcome of a call.

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 100%, so the comma-separated key format is already documented. The description adds batch semantics that the schema does not: the whole list is processed and only failing entries are named, implying per-item partial failure rather than all-or-nothing.

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 the specific verb and resource ('Archive issues') and immediately defines the effect in plain terms ('put finished work on the shelf so boards and searches show what is still live'). It is clearly separable from sibling unarchive_issues, archive_project, and delete_* tools.

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?

Explicitly gives the precondition (only issues in a done status may be archived), names the recovery path (unarchive_issues), and points to search_issues with the `archived in (true, false)` filter for finding archived items. It also covers the when-not case: non-done issues are refused.

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

All Kaiku tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?