Skip to main content
Glama

orchestrator_init

Initialize a long-running orchestration session to set up feature lists, progress tracking, and the environment for multi-hour autonomous coding tasks.

Instructions

Initialize a new long-running orchestration session. Call this first with a task description to set up the feature list, progress tracking, and environment.

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>",
      "taskDescription": "<taskDescription>"
    },
    "name": "orchestrator_init"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectDirYesAbsolute path to the project directory
taskDescriptionYesFull description of what needs to be built/accomplished
existingFeaturesNoOptional: List of feature descriptions if you've already analyzed the task

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 and does disclose the state it establishes (feature list, progress tracking, environment), which is genuinely useful. It omits the behaviors that matter most for an init tool: whether it writes files to projectDir, whether it fails or overwrites when a session already exists, and whether the operation is reversible.

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?

Two tight sentences with the ordering instruction front-loaded and no filler. Slightly more compact front-loading ('Call this first...') before the purpose statement would be marginally better, but nothing is wasted.

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 3-parameter, fully documented schema with no output schema, the description covers purpose, ordering, and the state it sets up. The main remaining gap is failure/idempotency behavior on a second invocation, which is relevant given the presence of orchestrator_reset and setup_init siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already defines all three parameters. The description still adds meaning by framing taskDescription as the seed for 'the feature list', which explains the relationship between the required task text and the optional existingFeatures array. Baseline 3 would understate the value added here; the framing that the task description drives feature generation is real semantic content 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?

States a specific verb and resource: 'Initialize a new long-running orchestration session', and names the concrete artifacts it creates (feature list, progress tracking, environment). It does not distinguish itself from the similarly named sibling setup_init or from orchestrator_reset, so an agent cannot fully resolve the choice from the description alone.

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?

'Call this first with a task description' gives explicit ordering guidance that is the key usage signal for an init tool. It stops short of stating exclusions, e.g. what to do if a session already exists or when setup_init/orchestrator_reset would be the correct entry point instead.

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