Skip to main content
Glama

record_fix

Close an issue after confirming a fix works, appending a fix record and clearing the active issue marker to prevent future conflicts.

Instructions

Record a confirmed fix and close the current issue.

Only call AFTER you have evidence the fix works (test passes, error
gone, user confirmed). Closing the issue clears the active-issue
marker so the next record_attempt won't silently latch onto this
closed issue (L-027a).

Side effects: appends a `fix` event, closes the active issue, and
clears the active-issue marker so the next record_attempt won't
silently latch onto a closed issue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryYesOne-line description of the confirmed fix (e.g., 'guarded submit handler with isSubmitting ref').
locationNoOptional file path or component where the fix was applied.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description fully discloses side effects: appends a fix event, closes the active issue, and clears the active-issue marker. This gives agents necessary behavioral context for a mutation tool.

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

Conciseness4/5

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

The description is front-loaded with purpose and conditions, but contains slight redundancy: the side effect about clearing the marker is repeated in both the second and third paragraphs. Still, it is well-structured overall.

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?

Given two parameters with full schema descriptions, an output schema (not needing explanation of return values), and comprehensive coverage of side effects and usage conditions, the description is complete for an agent's needs.

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%, so the baseline is 3. The description does not add additional meaning beyond what the input schema already provides for summary and location.

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 clearly states 'Record a confirmed fix and close the current issue,' which is a specific verb (record) and resource (fix/issue). It distinguishes from siblings like record_attempt, which is for unconfirmed attempts.

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 explicitly says 'Only call AFTER you have evidence the fix works' and explains that closing the issue clears the active-issue marker to prevent latching. This provides clear use context, though it does not explicitly name alternatives beyond implying record_attempt.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/riponcm/projectmem'

If you have feedback or need assistance with the MCP directory API, please join our Discord server