Skip to main content
Glama

headron

Read-onlyIdempotent

Run read-only CLI commands as argv when no dedicated tool fits, using exit codes as verdicts and batch mode for validated concurrent execution.

Instructions

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "headron"
  }
}

Input Schema

NameRequiredDescriptionDefault
argvNo
batchNo
parallelNoRun a validated read-only batch concurrently; defaults to ordered execution.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered structurally. The description adds genuinely non-redundant behavior: the exit code is the verdict, meaning success/failure must be read from the process status rather than the payload, and the JSON discovery command reveals valid arguments. It says nothing about how batch results or errors are surfaced, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core sentence is well front-loaded, but roughly half the text is a ~45-item verb dump that offers no semantics an agent can act on and is explicitly redundant with the recommended '["commands", "--json"]' discovery call. That enumeration crowds out more useful detail about argv and batch handling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should carry more weight on results, and it does supply the key exit-code contract. However, for a three-parameter escape-hatch tool, it leaves the batch/parallel interaction and failure reporting unexplained, so an agent still has to guess at multi-command behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%, and the only param with an inline description is 'parallel'. The description partially compensates by showing argv structure through examples ('mind --micro list', '["commands", "--json"]'), but it never explains the relationship between 'argv' and 'batch', nor that batch is capped at 8 commands and executes in order unless parallel is set.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The definition states a specific verb and resource ('Run a read-only Headron CLI command as argv') and explicitly positions itself as the fallback when 'no dedicated tool fits', which distinguishes it from siblings like gate, route, or proof. The long verb enumeration is incoherent as differentiation, but the core purpose statement is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit selection rule: use this only when no dedicated tool fits, which is exactly the fallback condition an agent needs. It also provides a discovery path ('["commands", "--json"] lists arguments'), though it does not say what to do when the argv is invalid or when a sibling is only partially suitable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.