Skip to main content
Glama

resume_session

Resume a paused or crashed swarm orchestration session by detecting dead workers, restoring a checkpoint, and continuing autonomous coding workflows.

Instructions

Resume a paused or crashed orchestration session. Handles crash recovery: detects dead workers, restarts from checkpoints, and resumes auto-orchestration.

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

Input Schema

NameRequiredDescriptionDefault
projectDirYesAbsolute path to the project directory
fromCheckpointNoSpecific checkpoint ID to restore from, or 'latest' (default: auto-detect)
restartDeadWorkersNoRestart workers that died during crash (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does add real behavioral detail beyond the name: detection of dead workers, checkpoint-based restart, and resumption of auto-orchestration. However it says nothing about preconditions (what happens if the session is already running), whether the operation is idempotent, what state is mutated, or what a failure looks like, so the mutation profile remains only partially disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences with the purpose front-loaded and recovery mechanics following. Every clause adds information and nothing is redundant.

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 three-parameter mutation tool with a fully documented schema and no output schema, the description covers purpose and recovery behavior adequately. The remaining gap is precondition and post-condition behavior for a state-changing operation, which matters more here because no annotations declare the safety profile.

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 coverage is 100%, so all three parameters are already documented, establishing a baseline of 3. The description adds no syntax, format, or interaction detail for projectDir, fromCheckpoint, or restartDeadWorkers, so it neither compensates for nor enhances the schema.

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 ('Resume a paused or crashed orchestration session') and scopes the trigger conditions precisely, so it is distinguishable from pause_session and shutdown_session without opening a schema. It stops short of naming any sibling explicitly, which keeps it from a 5.

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?

Gives a clear triggering context ('paused or crashed session') and describes the crash-recovery variant, so the agent knows when to reach for it. It offers no exclusions or counter-case (e.g., what to do instead when a session is still alive and healthy), which costs a point.

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