Kaiku

Set project paused

set_project_paused

Destructive

Pause a project — stop its work without taking anything away — or resume it. A paused project stays fully readable (board, issues, search, wiki, export) and accepts no writes from anybody, its lead and admins included, until it is resumed; reminders, schedules, agents and auto-archive leave it alone. Nothing about any issue or person changes. Only the project's lead (or its parent's, or an admin) may do either; both are written to the project's history. For a project whose work is finished, archive_project is the better word: it also takes the project off the lists.

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": {
      "projectKey": "<projectKey>",
      "paused": "<paused>"
    },
    "name": "set_project_paused"
  }
}

Input Schema

Name	Required	Description
`paused`	Yes	true to pause it, false to resume it.
`reason`	No	Optional, when pausing: why, in a sentence — shown on the board beside the notice. Up to 500 characters.
`projectKey`	Yes	Key of the project, e.g. 'AN'.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond destructiveHint=true: it discloses that reads stay open (board, issues, search, wiki, export), that all writes are blocked even for leads and admins, that reminders, schedules, agents and auto-archive skip the project, that issue and person data is untouched, and that the action is reversible until resumed. It also notes both pause and resume are recorded in project history. The 'nothing is taken away' framing clarifies rather than contradicts the destructive hint, since the description is explicit that state is mutated and writes are blocked.

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 core action and its scope, then permissions, then the routing hint — a sensible order. Minor redundancy between "without taking anything away" and "Nothing about any issue or person changes," and the read-surface list is long, but every sentence carries information.

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 two-required-parameter mutation with no output schema, the definition covers reversibility, side effects on automation, the permission model, audit implications, and the alternative tool. An agent has everything needed to call it correctly and to avoid misusing it as an archive.

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 coverage is 100% and each parameter is already documented, but the description reinforces the semantics of the boolean (pause vs. resume) and the conditional nature of reason. There is little left to add, so the high baseline applies without a compensating gap.

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 and resource in both directions ("Pause a project ... or resume it") and immediately scopes the meaning of pause: work stops but nothing is removed. It explicitly contrasts with archive_project, so an agent can discriminate the two without opening either schema.

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 explicit selection criteria against the nearest alternative ("For a project whose work is finished, archive_project is the better word") and states the prerequisite authority (project lead, parent lead, or admin). Both when-to-use and when-to-use-something-else are covered.

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?