Skip to main content
Glama

pause_session

Gracefully terminate all running workers and set the orchestration session status to paused to stop work temporarily.

Instructions

Pause the orchestration session. Gracefully kills all running workers and sets status to paused. Use when you need to stop work temporarily.

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": {
      "projectDir": "<projectDir>"
    },
    "name": "pause_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectDirYesAbsolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does well on the most important point by naming the destructive side effect ('gracefully kills all running workers') and the resulting state change, but it never says whether in-flight work is lost, whether the pause is reversible via resume_session, or what permissions are required.

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 short sentences, front-loaded with the action and its side effect before the usage hint. No filler, though the usage sentence could be folded into the first to tighten it further.

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 single-parameter, no-output-schema control tool, the description covers what it does, its destructive effect, and when to reach for it. The remaining gap is the reversibility story (that resume_session restores the session), which an agent would want before pausing.

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?

Only one parameter (projectDir) exists and the schema documents it at 100% coverage, so the baseline is 3. The description adds no meaning about the path or any constraints on it, but nothing is missing that the schema does not already cover.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Pause the orchestration session') and immediately clarifies the mechanism ('kills all running workers and sets status to paused'). It does not name resume_session or shutdown_session, so the agent must infer the distinction from the word 'temporarily' rather than an explicit contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use when you need to stop work temporarily' gives a clear triggering condition, and 'temporarily' implicitly separates it from a permanent shutdown. It stops short of naming the alternative tools or stating when not to use it (e.g., when work must be abandoned entirely).

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