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
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
headronB

One read-only headron command as argv, e.g. ["gate", "app.py", "--json"]. Verbs: commands, check, proof, invariants, doctor, index, learn, process, index-search, find, do, pick, decide, decide-engine, pipeline, judge, links, model, intake, shell, delegate, handoff, cadence, schedtargets, mind, sweep, role, resume, steps, failures, successes, md, landed, brainstorm, inspect, port, why, gate, route, compile, plan. ["commands", "--json"] lists each with its arguments; the exit code is the verdict.

portA

START HERE before editing a file: its route, tier, the gates to run, the lessons that apply, and the next commands. Read-only; the exit code is the verdict.

routeC

Which pack, card, manifest and rule resolved a path, and what else decides it. Read-only; the exit code is the verdict.

gateB

The one command a named gate runs for a file, as argv, with its state. It shows the command and does not run it. Read-only; the exit code is the verdict.

stepsC

The ordered implementation plan for one file, to its return point. Read-only; the exit code is the verdict.

failuresA

Mistakes agents made with a file (for) or with an error text (match), each with the guard that stops it. The whole ledger is not offered: scope it with for, match or one shape's id. Read-only; the exit code is the verdict.

successesC

The moves that replaced recorded failures, for a file (for) or one move (id), and how each is proved. Read-only; the exit code is the verdict.

proofA

Deterministic scope of a change to one file: its change class, planned gates and tools. Measured verification (--verify) runs gates and stays on the CLI. Read-only; the exit code is the verdict.

mind_classifyC

Classify files by change type and risk level using the Mind API orchestration layer.

mind_planA

Generate a verification plan for classified changes, listing gates and isolation needs.

mind_routeC

Select an authorized agent for a classified change based on capabilities and permissions.

mind_directC

One-shot orchestration directive combining classification, gates plan, agent route, policy rules, and search hits.

mind_searchA

Fast hybrid TF-IDF and symbol search across Headron using local index.

mind_healthA

Show Mind API health telemetry: session state, classification counts, and system status.

mind_receiptsB

Gather and verify audit receipts from Mind API operations over time.

Prompts

Interactive templates invoked by user choice

NameDescription
plan-changethe ordered steps that prove a change to one file, for this runtime
review-diffcheck a pasted diff against the gates its change class requires

Resources

Contextual data attached and managed by the client

NameDescription
versionatlas.yaml/version
identityatlas.yaml/identity
default_flowatlas.yaml/default_flow
hard_invariantsatlas.yaml/hard_invariants
forbidden_callsatlas.yaml/forbidden_calls
absent_input_ownersatlas.yaml/absent_input_owners
host_shapesatlas.yaml/host_shapes
enforcementatlas.yaml/enforcement
instrument_rosteratlas.yaml/instrument_roster
front_endatlas.yaml/front_end
instrumentsatlas.yaml/instruments
code_shapeatlas.yaml/code_shape
example_runnersatlas.yaml/example_runners
external_versionsatlas.yaml/external_versions
version_sitesatlas.yaml/version_sites
generated_filesatlas.yaml/generated_files
state_budgetsatlas.yaml/state_budgets
markdown_policyatlas.yaml/markdown_policy
stack_tiersatlas.yaml/stack_tiers
prompt_policyatlas.yaml/prompt_policy
brainstormatlas.yaml/brainstorm
portatlas.yaml/port
artifact_routesatlas.yaml/artifact_routes
routing_policyatlas.yaml/routing_policy
model_routesatlas.yaml/model_routes
context_policyatlas.yaml/context_policy
verification_policyatlas.yaml/verification_policy
decision_tablesatlas.yaml/decision_tables
build_orderatlas.yaml/build_order
build_order_ruleatlas.yaml/build_order_rule
task_profilesatlas.yaml/task_profiles
data_classesatlas.yaml/data_classes
artifact_edgesatlas.yaml/artifact_edges
knowledge_layersatlas.yaml/knowledge_layers
retrieval_policyatlas.yaml/retrieval_policy
asymmetriesatlas.yaml/asymmetries
parser_disciplineatlas.yaml/parser_discipline
governance_tiersatlas.yaml/governance_tiers
agent_failure_modesatlas.yaml/agent_failure_modes
success_kindsatlas.yaml/success_kinds
not_a_successatlas.yaml/not_a_success
agent_success_patternsatlas.yaml/agent_success_patterns
staleness_disciplineatlas.yaml/staleness_discipline
developer_baselineatlas.yaml/developer_baseline
tool_claimsatlas.yaml/tool_claims
linguist_namesatlas.yaml/linguist_names
process_conditionsatlas.yaml/process_conditions
project_manifestsatlas.yaml/project_manifests
runtime_entryatlas.yaml/runtime_entry
seatsatlas.yaml/seats
native_agent_toolsatlas.yaml/native_agent_tools
first_sweepatlas.yaml/first_sweep
topologiesatlas.yaml/topologies
drift_reviewatlas.yaml/drift_review
intentsatlas.yaml/intents
chatatlas.yaml/chat
language_selectionatlas.yaml/language_selection
pack_actionsatlas.yaml/pack_actions
process_stepsatlas.yaml/process_steps
processesatlas.yaml/processes
tool_profilesatlas.yaml/tool_profiles
language_mechanismsatlas.yaml/language_mechanisms
directory_scopesatlas.yaml/directory_scopes
agent_policyatlas.yaml/agent_policy
gate_alias_groupsatlas.yaml/gate_alias_groups
gate_toolsatlas.yaml/gate_tools
risk_modifiersatlas.yaml/risk_modifiers
authority_classesatlas.yaml/authority_classes
worktree_policyatlas.yaml/worktree_policy
branch_policyatlas.yaml/branch_policy
benchmark_floorsatlas.yaml/benchmark_floors
agent_rolesatlas.yaml/agent_roles
decision_evidence_backlogatlas.yaml/decision_evidence_backlog
cadenceatlas.yaml/cadence
delegation_contractatlas.yaml/delegation_contract
declared_inputsatlas.yaml/declared_inputs
public_surfaceatlas.yaml/public_surface
install_commandsatlas.yaml/install_commands
companionsatlas.yaml/companions
orphan_exemptionsatlas.yaml/orphan_exemptions
issue_route_termsatlas.yaml/issue_route_terms
issue_routesatlas.yaml/issue_routes
runtime_rolesatlas.yaml/runtime_roles

TDQS

B3.1/5.0

Scored across 15 tools

Disambiguation2/5

The generic headron tool can invoke the same verbs as port, route, gate, steps, failures, successes, and proof, so agents have no clear rule for choosing between the generic and specific tools. mind_direct also overlaps heavily with mind_classify, mind_plan, mind_route, and mind_search.

Naming Consistency3/5

The mind_* tools form a consistent prefixed family, and all names are lowercase snake_case, but the rest of the set mixes bare nouns (port, gate, proof, failures, successes) with a product name and no predictable verb_noun pattern.

Tool Count4/5

Fifteen tools is within a reasonable range for a workflow/orchestration server, but the generic headron command plus many thin wrappers means the count is slightly higher than needed.

Completeness4/5

The surface covers discovery, routing, gating, proof, failure/success lessons, agent selection, search, health, and receipts. It is missing explicit execution/verification tools, but the server is intentionally read-only, so the remaining gaps are minor.

Maintenance

ActivityActive
ResponsivenessNo issues