Skip to main content
Glama

Commit output

commit_output

Records the steering hash and applied pattern tags in local anti-repeat memory after delivering a result, helping prevent repeated outputs.

Instructions

Record a used steering hash and concrete pattern tags in the local anti-repeat memory. Call after delivering the result.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hash_id": "<hash_id>",
      "used_patterns": "<used_patterns>"
    },
    "name": "commit_output"
  }
}

Input Schema

NameRequiredDescriptionDefault
hash_idYesThe 16-hex HASH value from a steer_intent directive.
used_patternsYesConcrete patterns used in the result, e.g. 'supervision tree', 'gamelan polyrhythm'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world, non-idempotent write. The description adds genuinely useful context beyond them: the write target is a 'local anti-repeat memory' (scoped locally, not remote) and the correct invocation moment is post-delivery. It does not explain what happens on a duplicate hash or an invalid one, which matters given idempotentHint=false.

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

Conciseness5/5

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

Two short sentences with no filler; the what (record hash and tags) is front-loaded and the when (after delivery) follows immediately. Every clause carries information.

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

Completeness4/5

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

With only two fully described parameters, no nesting, no output schema, and annotations covering the safety profile, the description supplies what is needed to invoke correctly: purpose, write target, and timing. The remaining gap is failure/duplicate-call behavior, which is minor but non-trivial for a non-idempotent write.

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 100%, and the schema itself documents the 16-hex hash format, its origin in a steer_intent directive, the max of 12 patterns, and gives examples. The description only restates 'used steering hash' and 'concrete pattern tags', adding framing but no new semantics, so the baseline of 3 applies.

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 description uses a precise verb ('Record') and names both the resource written (a used steering hash plus concrete pattern tags) and the destination (local anti-repeat memory), which clearly separates it from steer_intent (which issues directives) and diversity_telemetry (which reports). It stops short of explicitly naming a sibling as the alternative, so it is clear but not maximally differentiated.

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?

'Call after delivering the result' gives an explicit trigger point in the workflow, which is the key timing decision for this tool. It offers no exclusion or when-not guidance (e.g., what to do if no steering hash was consumed), so it falls short of a 5.

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

Deploy Server

Other Tools