Skip to main content
Glama

orchestrator_reset

Terminates all worker processes and clears session state to recover or restart an orchestration run. Requires a project directory and explicit confirmation before resetting.

Instructions

Reset the orchestration session. Kills all workers and clears state. Use with caution!

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>",
      "confirm": "<confirm>"
    },
    "name": "orchestrator_reset"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to confirm reset
projectDirYesAbsolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the destructive effects (workers killed, state cleared), which is the single most important behavior, but it omits reversibility, whether on-disk project files are affected, and what a failed reset leaves behind.

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 consequences. The trailing "Use with caution!" is largely redundant given the explicit destruction statement, but nothing is verbose.

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 two-parameter tool with full schema coverage and no output schema, the key facts are present: it is destructive and unconditional. The main residual ambiguity is whether "clears state" includes persisted project files or only in-memory orchestration state.

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 description coverage is 100%, so both projectDir and confirm are already documented in structured form. The description adds nothing about parameter meaning (e.g., whether projectDir scopes which session is reset), so the baseline of 3 applies.

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 states a specific verb and resource ("Reset the orchestration session") and immediately qualifies scope with "Kills all workers and clears state." It is clearly distinguishable from orchestrator_init and orchestrator_status, though it never names a sibling explicitly.

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

Usage Guidelines2/5

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

"Use with caution!" is a warning, not guidance on when to invoke this versus alternatives such as pause_session, which is the obvious non-destructive sibling. No preconditions (session must be initialized, active work flushed) or exclusions are stated.

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