QA Orchestrator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QA_ORCHESTRATOR_DATA_DIR | No | Directory for QA Orchestrator data. | ~/.qa-orchestrator |
| QA_ORCHESTRATOR_MODEL_POLICY_PATH | No | Path to the model policy JSON file. | ~/.qa-orchestrator/model-policy.json |
| QA_ORCHESTRATOR_SESSION_STORE_PATH | No | Optional local SQLite file path to restore unfinished orchestration state after restart; disabled when unset. | |
| QA_ORCHESTRATOR_ORCHESTRATION_TTL_SECONDS | No | TTL in seconds for orchestration sessions. | 1800 |
| QA_ORCHESTRATOR_ORCHESTRATION_MAX_SESSIONS | No | Maximum number of active orchestration sessions. | 100 |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| prepare_qa_orchestrationA | Return a fixed checklist for one Use it for one scoped concern. For a selected bundle, request each Passing |
| start_qa_orchestrationA | Create a content-free QA session for a tracked review; call once before triage. Every call creates a separate session. Use prepare_qa_orchestration for a stateless profile
checklist.
|
| advance_qa_orchestrationA | Complete the active review step or mark an early stop; return the next action. Pass current_step as completed_step; stale or out-of-order steps are rejected. Malformed arguments, incompatible signals, and unknown or expired run_ids return errors without advancing the run. This call is non-idempotent: if a successful response is lost, inspect get_qa_orchestration before continuing; replaying the prior step is rejected.
|
| get_qa_orchestrationA | Read a session's current content-free state without changing it. Use this only to inspect a retained session's current step, next action, and model policy. Reads do not extend the TTL; an unknown or expired session cannot be recovered here, so start a new one. Use advance_qa_orchestration to change an active run or finish_qa_orchestration to record its final outcome. |
| finish_qa_orchestrationA | Finalize the host's outcome after synthesis or an early stop; no review step runs here. Call when advance_qa_orchestration reaches
This tool records the host's decision; it does not make it. |
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 5 tools
The five tools map to distinct lifecycle stages (prepare=stateless lookup, start=create session, advance=progress step, finish=terminal outcome, get=read state). The main risk is confusing prepare_qa_orchestration with start_qa_orchestration, but the descriptions explicitly disambiguate by stressing prepare is stateless and never creates a session. advance vs finish is also clarified by tying finish to the awaiting_host_outcome terminal state.
All five tools follow a strict verb_qa_orchestration pattern: start_, prepare_, advance_, finish_, get_. The convention is uniform across the entire set with no deviations or mixed casing.
Five tools is a tight, well-scoped set that exactly covers a session lifecycle plus a stateless helper. Each tool earns its place with no redundancy or padding.
The surface covers the full lifecycle (create, stateless lookup, progress, read, terminal finalize) and handles early stops. Minor gap: there is no explicit list/abort/cancel operation, though early stop is folded into advance + finish, so agents can still work around it.