Skip to main content
Glama

KnownFix

by io.github.b-hash88

Redeem a fix

get_fix

Get or redeem a fix after search_fixes or list_catalog identifies the id. Free samples return immediately. For a paid fix, call with the id alone to receive a free diagnosis preview, confidence and compatibility, dollar price, signed Base Pay USDC and exact-ETH offers, and one pay-and-redeem action; then call once more with the matching paymentTx and private paymentOffer. Never pay again merely because an existing proof is pending or denied.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesFix id from search_fixes or list_catalog
paymentTxNoBase Pay UserOperation hash for USDC or Base transaction hash for ETH; omit for free samples.
paymentOfferNoPrivate signed bearer token from search_fixes or get_offer; omit for free samples and never publish it.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
fixNo
tierNo
causeNo
errorNo
fixIdNo
titleNo
deniedNo
receiptNoMachine-readable receipt derived by KnownFix after signed-offer and Base proof verification; never accepted from caller input.
citationNo
purchaseNo
nextActionNo

TDQS

A4.1/5.0
Behavior4/5

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

Annotations indicate a non-read-only, non-idempotent operation, and the description adds useful behavioral detail: free samples return immediately, paid fixes involve a diagnosis preview plus pay-and-redeem action, and users must not pay again if a proof is pending or denied. This goes beyond the annotations without contradicting them.

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?

The description is dense but front-loaded with the main purpose, followed by the free/paid flow and a safety warning. Every sentence carries necessary information, though the paid-fix sentence is long and could benefit from bullet formatting.

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?

Given the complexity of a two-step paid flow, the description covers the required call sequence, parameter usage, security note about the private token, and the free-sample case. An output schema exists so return values do not need elaboration, and no critical invocation detail appears 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 describes each parameter, including origins and when to omit payment fields. The description reinforces sequencing but does not add substantial semantic meaning beyond what the input schema 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?

Description states the specific action 'Get or redeem a fix' and the resource (a fix identified via search_fixes or list_catalog). It clearly distinguishes this tool from search/list siblings and clarifies the two-step paid redemption flow.

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?

Provides explicit context: fixes come from search_fixes or list_catalog, free samples return immediately, and paid fixes require an initial id-only call followed by a second call with paymentTx and paymentOffer. It does not explicitly state when to prefer an alternative like get_offer, but the flow is clearly scoped.

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