Skip to main content
Glama

buggy_recheck

Re-run recorded bug triggers after code changes to report which defects remain failing, are fixed, regressed, or unreachable, so you can confirm a fix held.

Instructions

Re-run every recorded trigger and report what changed: still failing, now fixed, regressed, or unreachable because the code moved. 'regressed' means a defect that had been observed fixed is failing again, which is the signal worth acting on. Use this after making changes, or to decide whether a fix held.

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_recheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootNo
timeoutNoSeconds allowed per call. Default 2.
functionNoLimit to one function.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the whole burden. It does disclose the classification semantics and usefully defines 'regressed', but it never says whether replaying triggers executes code, mutates recorded state, requires a prior buggy_scan/recall, or what happens with zero recorded triggers.

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?

Three tight sentences, front-loaded with the action and result categories, then the definition of the one ambiguous term, then the usage cue. No filler; the 'regressed' gloss earns its space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a replay/verification tool with no annotations and no output schema, the outcome vocabulary substitutes well for a return spec. But the side-effect profile, prerequisites, and the 'root' parameter's meaning are all missing, which is a real gap for something that re-executes recorded triggers.

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?

Coverage is 67% — only 'timeout' and 'function' are documented in the schema, while 'root' has no description anywhere. The description adds no syntax, defaults, or scoping detail for any of the three parameters, so it fails to compensate for the undocumented 'root'.

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?

States a concrete verb and resource — re-run every recorded trigger — and enumerates the four outcome classes it reports (still failing, fixed, regressed, unreachable). That is far more specific than the sibling names alone, though it never explicitly contrasts itself with buggy_scan or buggy_repair.

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?

Gives clear timing guidance: 'after making changes' or 'to decide whether a fix held.' It does not say when NOT to use it or name an alternative tool for the initial discovery case, so it stops short of full routing guidance.

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