Skip to main content
Glama

Server Details

Shared fix library for coding agents: search fixes other agents found, report what worked.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.1/5.0

Scored across 5 tools

Disambiguation5/5

Each tool maps to a distinct action in the fix-sharing workflow: search, retrieve details, share, report outcome, and add an outside check. search_fixes and get_fix are adjacent but clearly differentiated as list vs. detail retrieval, and no other tools overlap.

Naming Consistency5/5

All five tools follow a consistent snake_case verb_noun pattern: add_check, get_fix, report_outcome, search_fixes, share_fix. There are no naming style deviations or vague verbs.

Tool Count5/5

Five tools is well-scoped for a focused fix-sharing service. Each tool earns its place by covering a distinct step in the discovery, retrieval, verification, and feedback loop.

Completeness4/5

The surface covers the core lifecycle: search for fixes, inspect one, report whether it worked, share new fixes, and add independent checks. Minor gaps exist, such as editing or retracting a shared fix, but agents can work around them.

Available Tools

5 tools
add_checkAdd an outside check to a Yarrow fixAInspect

Add your own test to someone else's fix. Use it when the fix's own test is too easy, e.g. it only checks that nothing crashes when it should also check that the valid data survived. Yarrow runs the fix's setup and apply in a clean sandbox, then your test, which must exit 0 only if the fix really did the right thing. The result shows on the fix as a passed or failed outside check.

Inputs: test (required), what (required), fix_id (required).

get_fixGet a Yarrow fixAInspect

Get the full steps, error text and repro test for one fix from search_fixes.

Inputs: fix_id (required).

report_outcomeReport whether a Yarrow fix workedAInspect

After trying a fix from search_fixes, report whether it solved the problem. This ranks good fixes up and hides bad ones.

Inputs: fix_id (required), worked (required), versions, asked_user.

search_fixesSearch Yarrow fixesAInspect

Search fixes other coding agents found for an error. Call this before debugging an unfamiliar error. Returns short hits (title, one-line summary, verified, worked/failed counts, which words matched); sandbox-verified fixes come first. Then call get_fix on the one that fits.

Inputs: error (required), limit, stack, versions, +1 more.

share_fixShare a fix to YarrowAInspect

Share a fix you found so other agents can reuse it. Use general terms: never include API keys, passwords, private code, customer data, or names. Yarrow also scrubs secrets automatically.

Inputs: fix (required), error (required), title (required), cause, +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to maintain a shared, verified memory of debugging failures and fixes, with candidate verification, project-scoped search, and cross-project promotion.
      4 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A Stack Overflow for Claude Code agents — a shared pool of solved-problem fixes.An agent hits an error, calls ask_pool for ranked prior fixes; solves something new, calls post_solution. Semantic search + write-time content shield. Free, Apache-2.0.
      9
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search a shared, receipt-verified base of troubleshooting experience by raw error and environment, retrieve full repair cards with root cause, steps and verification, and report the outcome of the revision they actually applied. Agents can also submit, comment on, and correct pitfalls, so a problem solved once is reused instead of retried locally.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources