Skip to main content
Glama

auto_orchestrate

Automatically schedule and monitor parallel workers by priority, dependencies, and health, running hands-free until all project features are complete.

Instructions

Automatically schedule and monitor workers based on priority, dependencies, and worker health. Runs hands-free until all features complete.

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

Input Schema

NameRequiredDescriptionDefault
strategyNoScheduling strategy (default: adaptive)
projectDirYesAbsolute path to the project directory
maxConcurrentNoMaximum concurrent workers (default: 5)
checkIntervalSecondsNoHow often to check worker progress in seconds (default: 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It does add valuable behavior beyond the name: the run is autonomous ('hands-free'), driven by priority/dependencies/worker health, and terminates only when all features complete – implying a long-blocking call. It does not say whether it can be interrupted, what happens on worker failure, or whether it is idempotent/resumable, which matters for a long-running orchestration loop.

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 what it does and followed by the key operational trait (runs to completion unattended). No filler or redundant restatement of the name.

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 long-running, unattended orchestration tool with no annotations and no output schema, the description covers the core loop but omits what the agent gets back, how the run can be stopped or resumed (pause_session exists), and failure semantics. Adequate to identify the tool, but not complete enough to call it confidently in edge cases.

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% and every parameter carries its own description plus defaults and an enum for strategy, so the schema already does the semantic work. The description adds no meaning about strategy trade-offs, concurrency effects, or polling interval behavior, 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 compound verb and resource – 'schedule and monitor workers' – and adds scope ('based on priority, dependencies, and worker health') plus a termination condition ('until all features complete'). It is clearly distinguishable from status/inspection siblings like orchestrator_status or check_all_workers, but it never explicitly names which sibling it complements or replaces.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no reference to orchestrator_init, pause_session, or check_all_workers as alternatives. The phrase 'Runs hands-free until all features complete' hints at a long-running blocking mode, but the agent must infer when this is appropriate versus the other orchestration tools.

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