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.

Start with port on the file you will edit: its route, gates, lessons and next commands. failures and successes take a file or an error text, never the whole ledger. The headron tool takes any other read-only command's argv; the exit code is the verdict.

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
headronA

Run a read-only Headron CLI command as argv when no dedicated tool fits; verbs: commands, check, proof, invariants, doctor, index, learn, process, index-search, find, do, pick, decide, decide-engine, pipeline, judge, revise, propose, links, model, intake, shell, delegate, handoff, cadence, schedtargets, mind, sweep, role, resume, steps, failures, successes, md, landed, brainstorm, inspect, data, task, port, why, gate, route, compile, plan. Programs: mind --micro list. ["commands", "--json"] lists arguments; 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. Successful structured results include the command record and exit code.

routeA

Explain how a file path resolves to a language pack: returns the rule, evidence, guide, manifest and precedence. Use port for the full pre-edit brief; mind_route selects an agent instead. Successful structured results include the command record and exit code.

gateA

Show the command and state for a file's named verification gate; it does not execute the command. Use steps for an ordered work plan. Successful structured results include the command record and exit code.

stepsA

Build an ordered work plan for one file, including its route and checks; no steps are executed. Tier, change class and runtime shape the plan. Use mind_plan for change classification and isolation guidance. Successful structured results include the command record and exit code.

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. Successful structured results include the command record and exit code.

successesA

Look up recorded practices that address recurring failures, including when to use them, evidence and proving instruments. Scope by file or task with for, or by pattern id; limit applies to for. Use failures for the corresponding mistake patterns. Successful structured results include the command record and exit code.

proofB

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. Successful structured results include the command record and exit code.

mind_classifyA

Classify a set of changed files by category and risk. Use proof for a single file's planned gates; this does not run verification.

mind_planA

Classify changed files and return Mind's planned gates and isolation needs. Use steps for an ordered file-specific work plan; neither runs checks.

mind_routeA

Select an agent and model tier for classified changes using capabilities and policy. Use route to explain a file's language pack; this does not authorize or execute an action.

mind_healthA

Show Mind API health telemetry, cache statistics, and system status.

mind_receiptsA

Retrieve verification receipts and their validity and verdicts. Locally this reads the last verification receipt, if present; a configured hosted service supplies its own results. Validity does not rerun checks. Use proof to plan verification.

mind_searchA

Search this repository's code index for a symbol, path or phrase; returns ranked file hits.

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
adaptive_recoveryatlas.yaml/adaptive_recovery
decomposition_policyatlas.yaml/decomposition_policy
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
glanceatlas.yaml/glance
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
pointersatlas.yaml/pointers
orphan_exemptionsatlas.yaml/orphan_exemptions
issue_route_termsatlas.yaml/issue_route_terms
issue_routesatlas.yaml/issue_routes
runtime_rolesatlas.yaml/runtime_roles

TDQS

A3.5/5.0

Scored across 14 tools

Disambiguation2/5

Port, steps, proof, gate, route, and the headron catch-all all operate on pre-edit planning/verification for a file, and their descriptions differentiate by nuance rather than clearly separate resource/action boundaries. The headron tool explicitly duplicates many dedicated verbs (proof, steps, failures, successes, port, gate, route, plan), so an agent could easily choose the wrong entry point.

Naming Consistency3/5

All names are lowercase snake_case and readable, but there is no consistent verb_noun convention: some are bare nouns (gate, steps, port, route, proof) while others use a mind_ prefix (mind_search, mind_receipts, mind_classify). The mix of prefixed and unprefixed families makes naming only partially predictable.

Tool Count4/5

Fourteen tools is within a reasonable range for a repo-analysis and verification server. However, several overlap-heavy planning tools (port, steps, proof, gate, route) reduce the sense that every tool earns its place, and the catch-all headron inflates the effective surface.

Completeness4/5

For a read-only change-planning and verification domain, the surface covers search, routing, gates, plans, receipts, failure/success lookup, and health telemetry. Missing direct execution or recording capabilities appear intentional or are handled through the CLI fallback, leaving only minor gaps.

Maintenance

ActivityActive
ResponsivenessNo recent community issues