Skip to main content
Glama

record_attempt

Record each fix attempt to track outcomes and prevent repeating mistakes. Automatically attaches to the active issue or creates one if none exists.

Instructions

Record a fix attempt on the current issue.

MANDATORY: call IMMEDIATELY after each distinct fix attempt — do NOT
batch multiple attempts into one call.

`outcome` must be 'worked', 'failed', or 'partial'. Pass `issue_id`
explicitly to attach to a specific issue; otherwise the attempt
attaches to the active issue. If no active issue exists, an implicit
parent issue is auto-created from this attempt's text (L-008).

Side effects: appends an `attempt` event and updates the issue file.
Does NOT close the issue — call record_fix for that.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
outcomeNoResult of the attempt. Must be exactly one of 'worked', 'failed', or 'partial'. Defaults to 'failed' — the safer default when an outcome is uncertain.failed
summaryYesOne-line description of what you tried (e.g., 'tried contain: layout — preview still jumps').
issue_idNoOptional zero-padded issue ID (e.g., '0042') to attach this attempt to. When omitted, attaches to the active issue; if no active issue exists, an implicit parent issue is auto-created from this attempt's text.
locationNoOptional file path or component touched by this attempt.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses side effects: 'appends an attempt event and updates the issue file,' and states it does NOT close the issue. Mentions auto-creation of parent issue and a behavior code (L-008). Could mention idempotency or multiple call effects, but still strong.

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?

Well-structured with bold emphasis on key points (MANDATORY, IMMEDIATELY). Sentences are informative and front-loaded. Minor repetition about auto-creation from schema, but overall efficient.

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 an output schema exists (not shown), the description need not detail return values. It covers purpose, usage guidelines, parameter details, side effects, and sibling differentiation. The behavior code L-008 adds specificity. Complete for agent use.

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 beyond schema, especially for outcome (explains the default and rationale) and issue_id (clarifies active issue logic). This extra context justifies a 4.

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 fix attempt on the current issue,' specifying the verb and resource. It explicitly distinguishes from sibling tool record_fix by noting that it does NOT close the issue. This differentiates it effectively from other tools like log_issue and add_decision.

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?

Provides explicit timing guidance: 'call IMMEDIATELY after each distinct fix attempt — do NOT batch multiple attempts into one call.' Also tells when to use record_fix instead for closing issues, and how issue attachment works (explicit id vs active issue vs auto-creation).

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