KnownFix

Create a signed purchase offer

get_offer

Read-onlyIdempotent

Create or refresh a one-hour signed bearer offer for a chosen skill, bundle, audit, or fix. Do not call this after a paid search_fixes result or an unpaid get_fix/get_skill result because those responses already include both payment rails. Choose USDC for Base Pay or ETH for exact wei; with no product arguments, this returns the general settlement document.

Input Schema

TableJSON Schema

Name	Required	Description
`currency`	No	Settlement rail. Defaults to ETH for backward compatibility.
`productId`	No	Exact fix, skill, bundle, or audit product id.
`productType`	No	Catalog shelf that owns the product id; bundles use skill.

Output Schema

TableJSON Schema

Name	Required	Description
`rule`	No
`spec`	No	Offer or settlement-document specification.
`error`	No	Machine-readable product, currency, or checkout failure.
`offer`	No
`payTo`	No
`token`	No	Private signed bearer purchase credential; never publish it.
`detail`	No	Human-readable failure detail.
`backend`	No
`basePay`	No
`catalog`	No
`chainId`	No
`network`	No
`currency`	No
`decimals`	No
`priceEth`	No
`priceUsd`	No
`priceWei`	No
`servedBy`	No
`expiresAt`	No
`productId`	No
`amountUsdc`	No
`paymentUri`	No
`redemption`	No
`settlement`	No
`productType`	No
`basePriceWei`	No
`usdcContract`	No
`tokenHandling`	No
`amountUsdcAtomic`	No
`baseAmountUsdcAtomic`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedAug 30, 2026

changedInput schema / properties / productType / enum

Previous value: -[
-  "fix",
-  "skill",
-  "audit"
-]New value: +[
+  "fix",
+  "skill",
+  "audit",
+  "service"
+]

changedOutput schema / properties / productType / enum

Previous value: -[
-  "fix",
-  "skill",
-  "audit"
-]New value: +[
+  "fix",
+  "skill",
+  "audit",
+  "service"
+]

Changed31 schema fields changedAug 27, 2026

changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +false
```
addedOutput schema / properties / amountUsdc
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / amountUsdcAtomic
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / backend

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

addedOutput schema / properties / baseAmountUsdcAtomic
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / basePay

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

addedOutput schema / properties / basePriceWei
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / catalog

Added value: +{
+  "format": "uri",
+  "type": "string"
+}

addedOutput schema / properties / chainId
```
Added value: +{
+  "type": "integer"
+}
```

addedOutput schema / properties / currency

Added value: +{
+  "enum": [
+    "USDC",
+    "ETH"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / decimals
```
Added value: +{
+  "type": "integer"
+}
```

changedOutput schema / properties / detail / description

Previous value: -"Human-readable error or status detail."New value: +"Human-readable failure detail."

changedOutput schema / properties / error / description

Previous value: -"Machine-readable error code, when the operation did not complete."New value: +"Machine-readable product, currency, or checkout failure."

addedOutput schema / properties / expiresAt

Added value: +{
+  "format": "date-time",
+  "type": "string"
+}

addedOutput schema / properties / network
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / offer

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

addedOutput schema / properties / payTo
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / paymentUri
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / priceEth
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / priceUsd
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / priceWei
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / productId
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / productType

Added value: +{
+  "enum": [
+    "fix",
+    "skill",
+    "audit"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / redemption

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

addedOutput schema / properties / rule
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / servedBy
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / settlement

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

addedOutput schema / properties / spec

Added value: +{
+  "description": "Offer or settlement-document specification.",
+  "type": "string"
+}

addedOutput schema / properties / token

Added value: +{
+  "description": "Private signed bearer purchase credential; never publish it.",
+  "type": "string"
+}

addedOutput schema / properties / tokenHandling
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / usdcContract
```
Added value: +{
+  "type": "string"
+}
```

Changed5 schema fields changedAug 27, 2026

addedInput schema / properties / currency

Added value: +{
+  "description": "Settlement rail. Defaults to ETH for backward compatibility.",
+  "enum": [
+    "USDC",
+    "ETH"
+  ],
+  "type": "string"
+}

changedInput schema / properties / productId / description

Previous value: -"Fix or skill id"New value: +"Exact fix, skill, bundle, or audit product id."

addedInput schema / properties / productType / description

Added value: +"Catalog shelf that owns the product id; bundles use skill."

changedInput schema / properties / productType / enum

Previous value: -[
-  "fix",
-  "skill"
-]New value: +[
+  "fix",
+  "skill",
+  "audit"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "detail": {
+      "description": "Human-readable error or status detail.",
+      "type": "string"
+    },
+    "error": {
+      "description": "Machine-readable error code, when the operation did not complete.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedAug 23, 2026

addedInput schema / properties / productId

Added value: +{
+  "description": "Fix or skill id",
+  "type": "string"
+}

addedInput schema / properties / productType

Added value: +{
+  "enum": [
+    "fix",
+    "skill"
+  ],
+  "type": "string"
+}

First observedAug 14, 2026

TDQS

A4.7/5.0

Behavior4/5

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

The description goes beyond the readOnly/idempotent annotations by disclosing the one-hour validity, bearer nature, and that no-arg calls return the general settlement document. The verb 'create' is slightly ambiguous with readOnlyHint, but the 'returns' language frames it as generating an ephemeral signed document rather than a persisted resource.

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, no filler. The central behavior and expiry are front-loaded, the exclusion rule follows, and currency/no-arg behavior closes with practical detail.

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?

With an output schema present and annotations already covering safety/idempotence, the description supplies the key decision-relevant context: when not to call, what no-args does, and what currency means. Nothing essential for correct invocation is left unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already describes the parameters. The description adds practical meaning: 'USDC for Base Pay or ETH for exact wei', the no-product argument variant, and confirmation of which product types map to which catalog shelves.

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 names a specific action ('Create or refresh') and a concrete resource ('one-hour signed bearer offer'), and scopes it to skill, bundle, audit, or fix. This makes it easy to tell apart from sibling tools such as get_fix/get_skill, which return catalog content rather than payment instruments.

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?

It explicitly states when not to call the tool ('Do not call this after a paid search_fixes result or an unpaid get_fix/get_skill result') and why (those responses already include payment rails). It also gives selection guidance for currency and defines the no-argument fallback.

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

All KnownFix tools Inspect

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.

Create a signed purchase offer

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources