Skip to main content
Glama

fix

Repairs unambiguous validation findings in place—broken links, dependency/related front-matter, and unlabeled open questions—while listing ambiguous items as unfixed; dry run by default.

Instructions

Repair the validate findings that have one obvious fix, editing text in place (never renaming or moving a file): a broken link whose filename matches exactly one initiative in its collection, depends_on / related front-matter (turned into links under ## Dependencies / ## Related), and open questions without a label (given the labels they are reported with). Anything ambiguous is listed in unfixed. Dry run by default: returns each edit (file, line, before, after); pass dry_run: false to write. Padding is fixed by repad, numbers by renumber.

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": "fix"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
collectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.6.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so well: it states that edits are in-place, files are never renamed or moved, dry run is the default, writes require `dry_run: false`, and dry-run output includes file, line, before, and after. It also discloses what happens to ambiguous findings via `unfixed`.

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?

Despite being one dense paragraph, it is front-loaded with the core purpose and every clause earns its place: fix categories, exclusions, ambiguous handling, dry-run behavior, return shape, and sibling-tool routing. There is no filler.

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

Completeness5/5

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

For a two-parameter repair tool with no annotations and no output schema, the description covers scope, exclusions, write safety, return shape, and ambiguity handling. An agent has enough information to decide when to call it and what to expect.

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

Parameters4/5

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

Schema coverage is 0%, so the description must explain both parameters. It thoroughly documents `dry_run` semantics (default true, false writes) and implies `collection` scopes the initiative matching used for broken-link repairs, but does not explicitly describe the `collection` parameter's role or format.

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

Purpose5/5

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

The description uses a specific verb ('Repair') tied to the output of `validate`, and enumerates exactly the three fix categories handled: broken links with unique filename matches, `depends_on`/`related` front-matter, and unlabeled open questions. It also distinguishes itself from sibling tools by naming `repad` for padding and `renumber` for numbers.

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

Usage Guidelines5/5

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

It clearly states that only findings with one obvious fix are repaired, that ambiguous cases appear in `unfixed`, and that padding and numbering are handled by other tools. It also explains the default dry-run behavior and the exact condition for writing (`dry_run: false`).

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