Skip to main content
Glama

record_attempt

Log each distinct fix attempt on an issue with its outcome and summary so agents track what worked, failed, or was partial and avoid batching attempts.

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "summary": "<summary>"
    },
    "name": "record_attempt"
  }
}

Input 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
projectNoWhich project this call is about — a registered id, alias, or absolute path (e.g. 'ossdrop'). Omit it when the server was started for a single repo, or when an active project is set with `pjm project use`. Call list_projects to see the registered names.
summaryYesOne-line description of what you tried (e.g., 'tried contain: layout — preview still jumps'). Put further evidence into another attempt, not this one. Keep it under 300 characters: summary.md clips longer text.
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

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.5
    • changedInput schema / properties / summary / description
      Previous value: -"One-line description of what you tried (e.g., 'tried contain: layout — preview still jumps')."New value: +"One-line description of what you tried (e.g., 'tried contain: layout — preview still jumps'). Put further evidence into another attempt, not this one. Keep it under 300 characters: summary.md clips longer text."
  2. Changed1 schema field changedv0.3.2
    • addedInput schema / properties / project
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Which project this call is about — a registered id, alias, or absolute path (e.g. 'ossdrop'). Omit it when the server was started for a single repo, or when an active project is set with `pjm project use`. Call list_projects to see the registered names.",
      +  "title": "Project"
      +}
  3. Changed5 schema fields changedv0.1.3
    • addedInput schema / properties / issue_id / description
      Added value: +"Optional 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."
    • addedInput schema / properties / location / description
      Added value: +"Optional file path or component touched by this attempt."
    • addedInput schema / properties / outcome / description
      Added value: +"Result of the attempt. Must be exactly one of 'worked', 'failed', or 'partial'. Defaults to 'failed' — the safer default when an outcome is uncertain."
    • addedInput schema / properties / outcome / pattern
      Added value: +"^(worked|failed|partial)$"
    • addedInput schema / properties / summary / description
      Added value: +"One-line description of what you tried (e.g., 'tried contain: layout — preview still jumps')."
  4. First observedv0.1.1

TDQS

A4.6/5.0
Behavior5/5

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

With zero annotations, the description carries the full burden and does so: it declares the writes ("appends an `attempt` event and updates the issue file"), the latent side effect (implicit parent issue auto-created when no active issue exists), and the operation it does not perform. Minor omissions exist (idempotency, error behavior) but the mutation surface is disclosed.

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?

Front-loaded with the action and the mandatory timing rule, then side effects and the boundary with record_fix. Every clause is functional; the internal reference "(L-008)" is the only noise an agent cannot act on.

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 5-parameter mutation with no annotations, the description covers trigger, scoping fallback, written artifacts, and the excluded follow-up, while the output schema covers return values and the schema covers field syntax. Nothing needed to invoke it correctly is missing.

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 coverage is 100% and the schema already specifies the outcome enum/pattern, the issue_id fallback chain, and the summary length guidance. The description largely restates those constraints (allowed outcome values, issue_id vs. active issue) rather than adding format or precedence detail, so it earns the baseline for a fully documented schema.

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?

States a specific verb and resource ("Record a fix attempt") and immediately bounds it against the sibling that does more: "Does NOT close the issue — call record_fix for that." An agent can distinguish record_attempt from record_fix, log_issue, and search_events without opening any schema.

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?

Gives an explicit trigger ("call IMMEDIATELY after each distinct fix attempt") plus an explicit anti-pattern ("do NOT batch multiple attempts into one call"), and names the alternative tool for the adjacent need. When-to-use and when-not-to-use are both present with no inference required.

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