Skip to main content
Glama

orchestrator_status

Retrieve the current orchestration session status to restore state after context compaction or check swarm progress.

Instructions

Get the current status of the orchestration session. Call this after context compaction to restore state, or anytime to check progress.

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

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format: 'compact' for minimal output (no emoji/decorators), 'pretty' for full formatting (default)
projectDirYesAbsolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 burden. It implies a safe read ('Get') and usefully discloses the post-compaction state-restoration role, but says nothing about what the status report contains, whether state is cached, or any access requirements.

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?

Two short sentences, front-loaded with the core action and followed by the trigger condition. No filler or restated metadata; every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read tool this covers purpose and timing adequately, but with no output schema the definition never indicates what the returned status contains (progress fields, session state, worker info), leaving the agent unsure what to expect back.

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 the format enum are already fully documented in the schema. The description adds no syntax or behavioral detail beyond that, which is the expected baseline when the schema does the work.

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: 'Get the current status of the orchestration session.' An agent can tell this reads session state rather than creating or mutating it, implicitly distinguishing it from orchestrator_init and orchestrator_reset by name family, though no sibling is named explicitly.

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 an explicit trigger ('after context compaction to restore state') plus a general use case ('anytime to check progress'), which tells the agent exactly when this tool is the right call. It stops short of stating exclusions or pointing at alternative status tools like protocol_status or get_session_stats.

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