Skip to main content
Glama
Sign In

Kaiku

by tech.kaiku.mcp
OverviewDiscussionsAdmin

Unarchive issues

unarchive_issues
Destructive

Take archived issues back off the shelf, onto the board and into default searches. Never refused for the state an issue stands in. Takes a full member of each issue's project; a paused or archived project refuses every write — take the project itself out of the archive with unarchive_project.

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": "unarchive_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysYesIssue keys, comma-separated: 'AN-1, AN-2'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the write/destructive annotations, it discloses the permission requirement, the behavior under paused or archived projects, and that the call is never refused for the issue's own state, which is non-obvious and useful. It stops short of explaining batch failure semantics, e.g., whether bad or already-active keys abort the whole call.

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?

Three tight sentences with the effect front-loaded, followed by the state caveat and the permission/alternative caveat. The 'off the shelf' phrasing is colorful but not wasteful; nothing needs to be cut.

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 one-parameter write tool with no output schema, the description covers effect, permissions, and the main blocker. The only remaining gap is what happens with invalid or already-unarchived keys and whether the operation is atomic across a key list.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single 'keys' parameter already documents the comma-separated format 'AN-1, AN-2'. The description adds no additional meaning about key handling, so the baseline 3 is appropriate.

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 states a specific verb and resource plus the concrete effect: archived issues come back 'onto the board and into default searches.' It also distinguishes itself from the nearest sibling by naming unarchive_project as the different tool for the project-level case.

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?

It gives an explicit precondition ('full member of each issue's project') and an explicit when-not with the alternative: if the project is paused or archived, every write is refused and you should call unarchive_project instead. Nothing about tool selection is left to inference.

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

All Kaiku toolsInspect
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