Skip to main content
Glama

record_fix

Record a confirmed fix and close an issue. Provide a summary of the fix and optionally specify the issue ID or location.

Instructions

Record a confirmed fix and close an issue.

Only call AFTER you have evidence the fix works: test passes, error is gone,
or the user confirmed.

If `issue_id` is provided, the fix is attached to that specific issue.
If `issue_id` is omitted, the active issue is closed.

Side effects: appends a `fix` event and updates summary.md. The active-issue
marker is cleared only when the active issue is the issue being fixed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryYesOne-line description of the confirmed fix (e.g., 'guarded submit handler with isSubmitting ref').
issue_idNoOptional zero-padded issue ID (e.g., '0042') to close. When omitted, closes the active issue. Numeric strings without padding are accepted.
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?

Without annotations, the description fully discloses side effects: appending a 'fix' event, updating summary.md, and clearing the active-issue marker only when the active issue is the one being fixed. This gives the agent clear expectations.

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?

The description is extremely concise with four sentences, each adding meaningful information. It is front-loaded with the purpose, making it efficient for an agent to parse.

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 simple tool with 3 parameters (1 required) and an output schema, the description covers all essential aspects: purpose, usage conditions, parameter behavior, and side effects. No gaps are present.

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 100%, so baseline is 3. The description adds value by clarifying the behavior of `issue_id` (attach to specific vs. active issue), which goes beyond the schema's 'optional' description. However, it does not add significant detail for `summary` or `location` beyond what the schema provides.

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 the tool records a confirmed fix and closes an issue, distinguishing it from siblings like 'record_attempt' (which logs attempts) and 'log_issue' (which logs issues). The verb 'record' and resource 'fix' are specific.

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?

The description explicitly instructs to call only after evidence of a working fix (test passes, error gone, user confirmation). It also explains the behavior when `issue_id` is provided versus omitted, guiding the agent's choice.

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