Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
submit_goalC

Submit a high-level goal to be decomposed, implemented, and verified.

execute_runC

Execute the full supervised PM/Developer/QA lifecycle for a submitted run with explicit commands.

execute_taskC

Execute a specific task in a run through the supervised workflow and return evidence.

get_runB

Read summary status and task count for a given run.

list_tasksA

List all tasks in a run with their status, role, and dependencies.

get_task_evidenceB

Retrieve verified executor receipts and QA verdicts for a specific task.

get_pending_approvalsA

List all pending actions requiring human approval under CHAT_APPROVAL mode.

reject_approvalC

Reject a pending gated action.

cancel_runB

Cancel an active run and mark its tasks cancelled.

get_model_usageA

Aggregate token and cost usage across active budget ledgers and sessions.

discover_modelsB

Discover available models and their capabilities from the local 9Router instance.

list_skillsC

List approved, pinned skills and discovered skills for a specific role or workspace.

spawn_agentC

Legacy helper: create a new background subagent session on the given backend runner.

send_messageC

Legacy helper: queue a prompt for a session.

wait_for_idleC

Legacy helper: block until the session is idle/done/error or times out.

get_agent_statusD

Legacy helper: session diagnostics.

list_agentsC

Legacy helper: list diagnostics for every known session.

kill_agentC

Legacy helper: force-terminate a session's subprocess immediately.

reject_actionC

Legacy alias: reject a pending action.

list_pending_actionsC

Legacy alias: list pending actions.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.7/5.0

Scored across 20 tools

Disambiguation3/5

The core lifecycle tools (submit_goal, execute_run, execute_task, list_tasks, get_task_evidence, get_run) are reasonably distinct, but the surface contains explicit duplicates: get_pending_approvals vs list_pending_actions and reject_approval vs reject_action are the same operation, and the six 'legacy helper' agent/session tools overlap conceptually with the new run/task tools. The 'Legacy' labels in descriptions help an agent pick the modern path, but they do not remove the redundancy.

Naming Consistency4/5

Nearly everything follows a snake_case verb_noun pattern (submit_goal, list_tasks, cancel_run, get_model_usage), which is predictable and readable. Minor deviations like wait_for_idle and get_agent_status, plus vocabulary drift between 'agent', 'session', 'run', and 'task' for related concepts, keep it from a perfect score.

Tool Count3/5

20 tools is heavy for the apparent scope, and roughly a third of them (spawn_agent, send_message, wait_for_idle, get_agent_status, list_agents, kill_agent, reject_action, list_pending_actions) are deprecated legacy duplicates or aliases rather than new capability. The set would be better scoped near a dozen tools without the legacy tail.

Completeness3/5

The goal-to-run-to-task-to-evidence lifecycle, cancellation, approvals listing, model discovery, skills, and usage accounting are covered. However, the approval workflow is one-sided: there is get_pending_approvals and reject_approval but no tool to approve an action, which is a hard dead end under CHAT_APPROVAL mode, and there is no retry/resume for a failed task.

Maintenance

ActivityMaintained
ResponsivenessResponsive