Skip to main content
Glama

buggy_recall

Reports defects previously proven against a function, whether each was fixed, and whether any returned. Call before editing a risky function to avoid reintroducing a fixed bug.

Instructions

Report what is already known about a function: defects previously proven against it, whether each was later observed fixed, and whether any came back. Call this BEFORE editing a risky function, so a defect that was already fixed once is not reintroduced. Answers come from stored triggers that can be re-run, not from remembered advice.

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

Input Schema

NameRequiredDescriptionDefault
rootNoProject root holding .buggy/. Defaults to the current directory.
functionNoFunction to look up. Omit to list everything recorded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does add real value: answers are derived from stored, re-runnable triggers rather than model memory, which signals the results are grounded and reproducible. However, it never states that the call is read-only, whether re-running triggers has cost or side effects, or what latency to expect from a trigger re-run — meaningful gaps for a tool that may execute stored logic.

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?

Three sentences, each earning its place: the first defines the return payload, the second gives the call timing, the third establishes provenance. The most decision-relevant content (what you get) is front-loaded before the when-to-call guidance.

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?

There is no output schema, so the description must sketch return values — and it does, covering defect identity, fix status, and regression status. For a two-parameter, all-optional lookup that omission makes it nearly self-sufficient; only the absence of any read-only/cost reassurance keeps it from being fully complete.

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 both parameters (root, function) are fully described in the schema, including the default and the omit-to-list-everything behavior. The description adds no parameter-level meaning beyond that, so the baseline of 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?

The description names a specific verb and resource — report known defects for a function — and enumerates the payload (prior defects, whether each was observed fixed, whether any regressed). That is far more than a restatement of the name. It does not explicitly contrast with buggy_investigate or buggy_recheck, so sibling differentiation is only implied through phrases like 'already known' and 'stored triggers'.

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 gives a clear, actionable trigger condition: 'Call this BEFORE editing a risky function, so a defect that was already fixed once is not reintroduced.' That tells an agent exactly when to reach for it. It stops short of naming an alternative tool or stating when not to use it (e.g. first-time investigation of an unfamiliar function).

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