Orchestrator Python MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| orchestrate_initB | Initialize a new orchestration session with HMAC anti-tamper security. |
| orchestrate_statusB | Query current session status and active phase. |
| orchestrate_approveC | Grant human approval for the current phase deliverable. |
| orchestrate_verifyB | Run machine verification on current phase deliverables and advance phase on success. |
| orchestrate_archiveC | Archive current orchestration deliverables and release session lock. |
| orchestrate_get_dag_batchesB | Compute topological execution batches from plan.md tasks. |
| orchestrate_get_agentsA | List all specialized orchestrator agent personas. Each |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct operation: session init, status, human approval, machine verification, archiving, DAG batch computation, and agent listing. There is no meaningful overlap, and the approve versus verify distinction is clear because one is human-driven and the other is machine-driven.
All tools share the orchestrate_ prefix and lowercase snake_case, which makes the set easy to predict. However, status reads as a noun rather than an action verb, and the get_* retrieval tools stand slightly apart from the other lifecycle verbs.
Seven tools is well-scoped for an orchestration lifecycle server, covering session creation, status, approval, verification, archival, DAG computation, and agent discovery without redundancy. The count feels appropriate for the domain.
The core lifecycle is present, but the human-in-the-loop workflow lacks explicit reject, cancel, or rollback paths, and verification only advances on success. Additionally, the DAG batch and agent listing tools are auxiliary and do not include an execution tool, leaving a notable gap in the orchestration loop.