Skip to main content
Glama

pause_run

Pauses a running session after its current pass finishes so no further pass starts, and spends nothing. Record who requested the pause, then resume later with just the run id.

Instructions

Ask a RUNNING run to pause after the pass it is in: it finishes that pass, then stops before the next one starts (run_status reads it as owner_paused). The stop spends nothing; the person decides when to go on, and resume_run with only the run id continues it. Pass person_words, the person's own answer as they typed it, when the person asked for the pause; pass reason, your own, when you ask on your own account; never both, and one of them is required (a session is never the person at a terminal). Refuses a run nobody is running, a member of a tree, and a request that is already open. Nothing is recorded on a refusal.

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": {
      "run": "<run>"
    },
    "name": "pause_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
runYes
reasonNo
person_wordsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.4

TDQS

A4.8/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 behavioral burden and does so well: it explains the pass-boundary pause, the resulting owner_paused status, that the stop spends nothing, how resume works, the mutual-exclusivity requirement for the two justification fields, and that nothing is recorded on refusal.

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?

The description is a single dense paragraph that front-loads purpose and behavior, and every sentence adds value about cost, parameter rules, or refusal conditions. It could be easier to scan with bullets or shorter clauses, but there is no wasted wording.

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?

Given a mutation-like control tool with no annotations, no output schema, and three parameters, the definition covers state transitions, cost, continuation, parameter usage, refusal conditions, and recording behavior. Only the exact success acknowledgment/return shape is left implicit, which is a minor omission relative to the overall completeness.

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%, so the description must compensate. It clearly defines person_words as the person's own typed answer and reason as the agent's own, states mutual exclusivity and requiredness, and implies run is the run id via 'resume_run with only the run id'. The run parameter's format or identifier semantics are not explicitly spelled out, so it stops short of a 5.

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 ('Ask a RUNNING run to pause') and precisely defines the timing ('after the pass it is in: it finishes that pass, then stops before the next one starts'). It contrasts the resulting state with run_status reading it as 'owner_paused', so an agent can distinguish this from siblings like resume_run.

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 explicit conditions for the two optional parameters: person_words when the person asked for the pause, reason when the agent asks on its own account, never both, and one is required. It also names resume_run as the continuation path and lists refusal cases (not running, tree member, already-open request), leaving little to infer.

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