Skip to main content
Glama

Suggest fixes

suggest_fixes
Read-onlyIdempotent

Generate unified diffs and byte-range edits that correct mechanical lint findings in markdown steering files, so you can apply targeted fixes without rewriting files or risking automatic writes.

Instructions

Suggest fixes for mechanical lint findings (invisible and bidirectional characters, skill name fields, frontmatter not on line 1, HTML comments that give the agent instructions, trailing whitespace, a missing final newline) as a unified diff plus byte-range edits. It never writes. Apply the edits with minimal Edit calls, never by rewriting the whole file.

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

Input Schema

NameRequiredDescriptionDefault
pathNoOne file; omit for every steering file
pathsNoSeveral files
rulesNoOnly fixes for these rule ids
safetyNosafe: only fixes that cannot change meaning. all (default): also fixes to review

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false, so 'It never writes' reinforces rather than reveals. The description does add value beyond structured fields by disclosing the return shape (unified diff plus byte-range edits) and prescribing a consumption pattern of minimal Edit calls.

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 sentences, front-loaded with the action and scope, followed by the behavioral constraint and the application guidance. The parenthetical rule list is dense but every listed class carries information an agent needs to predict what the diff will touch.

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 no output schema, the description correctly explains the return value as a unified diff plus byte-range edits, and the annotations carry the safety profile. Minor gaps remain around scope defaults (one file versus all steering files) and how the safe/all setting affects the diff, though the schema covers both.

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 description coverage is 100%, including the safe/all default and the per-parameter meanings, so the schema does the heavy lifting. The description mentions the defect classes that correspond to the rules filter but adds no syntax or selection detail beyond the schema. Baseline 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?

Names a specific verb+resource ('suggest fixes for mechanical lint findings') and enumerates the exact rule classes covered (invisible/bidirectional characters, frontmatter placement, HTML comments, trailing whitespace, missing final newline). It also states the output form (unified diff plus byte-range edits). It never names a sibling such as lint_steering, so the distinction from the reporting tool is only implicit.

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?

Gives a clear post-invocation workflow: 'It never writes' and 'Apply the edits with minimal Edit calls, never by rewriting the whole file.' That is strong guidance on how to act on the result. It stops short of stating when to call this instead of lint_steering or how to choose between them.

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