Skip to main content
Glama

shutdown_session

Gracefully shuts down an orchestration session by creating a checkpoint, stopping workers after the current iteration, and writing a shutdown record so the session can be resumed later.

Instructions

Gracefully shut down the orchestration session. Creates a checkpoint, stops all workers (letting current iteration finish), and writes shutdown record. Use before closing laptop for resume_session recovery later.

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

Input Schema

NameRequiredDescriptionDefault
checkpointNoCreate a checkpoint before shutdown (default: true)
projectDirYesAbsolute path to the project directory
waitSecondsNoSeconds to wait for workers to finish current iteration (default: 60)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/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 and does well: it states the ordered side effects (checkpoint, graceful worker termination, shutdown record) and clarifies that workers are allowed to finish their current iteration rather than being killed mid-task. It omits what happens if workers exceed the wait window, whether shutdown is reversible, and what the call returns.

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 effects before the usage hint. Every sentence carries information; the phrasing is slightly informal ('closing laptop') but not wasteful.

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 terminal session operation with no output schema and no annotations, the description covers purpose, effects, sequencing behavior, and the primary use case, which is enough for an agent to invoke it correctly. Remaining gaps are secondary: failure modes on timeout and confirmation/return behavior.

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 with types, defaults, and bounds. The phrase 'letting current iteration finish' loosely reinforces the semantics of waitSeconds and checkpoint, but no new detail (e.g., what happens at waitSeconds=0, or what a skipped checkpoint costs) is added beyond 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?

The description opens with a specific verb and resource ('Gracefully shut down the orchestration session') and enumerates the concrete effects: checkpoint creation, worker stop, shutdown record. It implicitly contrasts with resume_session by framing the tool as preparing for later recovery, but never explicitly names pause_session, which is the closest sibling an agent might confuse it with.

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

Usage Guidelines3/5

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

One usage scenario is given ('Use before closing laptop for resume_session recovery later'), which is genuinely helpful context. However, there is no guidance on when NOT to use it and no mention of pause_session as the non-terminal alternative, so an agent must infer the boundary between pausing and shutting down.

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