Skip to main content
Glama

KnownFix

by io.github.b-hash88

Search verified fixes

search_fixes
Read-onlyIdempotent

Use this first for an exact error or distinctive symptom. Returns up to three confident ranked matches. A free top match includes the full fix. A paid top match includes a free diagnosis, confidence and compatibility, dollar price, signed USDC/Base Pay and exact-ETH rails, and one pay-and-redeem action; do not call get_offer. Use list_catalog to browse, get_fix only with a known id or payment proof, and request_fix only after an honest miss.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesPreserve the exact error code and distinctive text; add tool or runtime context needed to disambiguate it. Omit credentials, tokens, private hostnames, and private paths.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
fixNoFull fix, present only when the top match is free.
missNo
queryYesThe exact query that was evaluated.
matchesYesConfident ranked matches; empty means KnownFix is not claiming a match.
purchaseNoPurchase-ready diagnosis, signed offers, payment rails, and the single next action for a paid top match.
topMatchTierNo

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds meaningful behavioral detail: up to three ranked matches, what a free top match includes, what a paid top match includes, and the explicit instruction not to call get_offer. This goes well beyond the annotation baseline.

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?

The description is front-loaded with the most important usage rule, followed by return behavior, then sibling routing. Every sentence earns its place, and the dense second sentence packs essential free/paid distinction and redemption behavior without unnecessary filler.

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 one parameter, rich annotations, and an output schema, the description covers all necessary context: when to use, what results look like, how paid vs free matches behave, and how to route to alternatives. No critical calling information 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?

The single query parameter already has 100% schema coverage with detailed guidance on preserving exact error text, adding disambiguating context, and omitting sensitive data. The tool description restates the triggering condition but does not add substantial new parameter semantics beyond what the schema already provides.

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 the tool's action (search), resource (verified fixes), and when to use it (exact error or distinctive symptom). It also differentiates from siblings by naming list_catalog, get_fix, and request_fix as alternatives with distinct conditions.

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?

Explicit guidance is provided: use this first for exact errors, browse with list_catalog, use get_fix only with a known id or payment proof, use request_fix only after an honest miss, and explicitly do not call get_offer. This gives an agent clear routing rules with no ambiguity.

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

All KnownFix toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation4/5

Most tools target clearly distinct resources or actions, and cross-references like 'use get_fix instead' sharply reduce confusion. A minor source of ambiguity is the cluster of redemption/offer tools (get_fix, get_skill, get_offer) and the three status-check tools, but their descriptions disambiguate them well.

Naming Consistency5/5

All tools follow a consistent lowercase snake_case verb_noun pattern: audit_, check_, get_, list_, order_, request_, search_, submit_. The naming style is uniform and predictable across different domains.

Tool Count4/5

At 17 tools, the surface is slightly above the ideal 3-15 range but remains justified given the server's broad scope: catalog browsing, paid redemption, audits, services, requests, submissions, and checkout support. It is dense but not bloated.

Completeness4/5

The lifecycle coverage is strong: discover, get, request, submit, check status, order, pay, and redeem are all represented. Minor gaps exist, such as no cancellation/refund path, no way to update a submitted fix, and merch ordering delegated entirely to an external storefront.

Resources