Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
QA_ORCHESTRATOR_DATA_DIRNoDirectory for QA Orchestrator data.~/.qa-orchestrator
QA_ORCHESTRATOR_MODEL_POLICY_PATHNoPath to the model policy JSON file.~/.qa-orchestrator/model-policy.json
QA_ORCHESTRATOR_SESSION_STORE_PATHNoOptional local SQLite file path to restore unfinished orchestration state after restart; disabled when unset.
QA_ORCHESTRATOR_ORCHESTRATION_TTL_SECONDSNoTTL in seconds for orchestration sessions.1800
QA_ORCHESTRATOR_ORCHESTRATION_MAX_SESSIONSNoMaximum 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

CapabilityDetails
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

NameDescription
prepare_qa_orchestrationA

Return a fixed checklist for one agent_profile. It gives review focus, required output sections, shared evidence constraints, and escalation signals.

Use it for one scoped concern. For a selected bundle, request each review_profiles member separately in session order; use start_qa_orchestration to track the multi-concern review.

Passing agent_profile never selects a session profile. This stateless lookup does not inspect repository content, run the review, or change session state; the host owns final decisions.

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. task_type narrows the bundle shortlist; the host still selects the review route.

  • Sessions expire after the configured TTL (1800 seconds by default).

  • Capacity is 100 sessions by default and can be configured.

  • Expired sessions are purged and retained terminal sessions may be evicted. If capacity can only be freed by removing an active session, the call returns a session limit error.

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.

  • Completed triage requires exactly one of selected_bundle or selected_profile; omit both when stopping early.

  • After each completed primary review, send current_profile as completed_profile. On the final profile, also send risk_signals ({} if none apply); omit both on an early stop.

  • An early stop records partial or blocked but still needs finish_qa_orchestration with the same outcome. After synthesis, use finish_qa_orchestration for the host's final outcome.

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 awaiting_host_outcome after synthesis, or after it records an early stop. For an early stop, submit the same partial or blocked outcome.

  • Repeating the same outcome returns the retained terminal session. A conflicting outcome is rejected with conflicting final outcome and leaves the stored status unchanged.

  • Retention ends when the configured TTL expires (1800 seconds by default), a terminal session is evicted to free capacity, or the service restarts. After removal, the run_id is unavailable and the outcome can no longer be deduplicated.

This tool records the host's decision; it does not make it.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.7/5.0

Scored across 5 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive