Skip to main content
Glama

Thread Kit: posts that fit every network

Rewrite your x402 API listing copy so agent routers match it, with an OpenAPI patch (AI) ($0.250)

rewrite_x402_listing
Read-only

For sellers of paid APIs. Same audit, then an open model rewrites the operationId, summary, description and tags of up to 5 operations (worst first) from your own listing only; sentences with numbers or links not in your listing, or hype words, are removed. Returns before/after with score and task-word coverage, and a JSON merge patch for openapi.json. AI-written, not human-reviewed. No openapi.json or no usable model output is not charged. PAID: $0.250 per call in USDC on Base via x402 over MCP, or from prepaid credits if this server is configured with an Authorization: Bearer tkc_... header (see payment_options).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "origin": "<origin>"
    },
    "name": "rewrite_x402_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoOptional: what a buyer would ask a router for, in their words (max 160 characters), e.g. "split text into an X thread"; the report shows which operation matches it best and which words are missing.
originYesHost of the paid API to audit, e.g. api.example.com or https://api.example.com/v1/tool (a path is probed first). "sample" = a built-in example listing (no network request).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the sanitization rule (sentences with numbers/links not in the listing, or hype words, are removed), that output is AI-written and not human-reviewed, the exact price and payment rails, and the no-charge conditions. The non-determinism implied by idempotentHint=false is consistent with the AI-rewrite disclosure, with no contradiction.

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?

Front-loaded with the audience and action, and every clause carries information the agent needs (limits, sanitization, billing, failure charges). The pricing sentence is dense and long, but trimming it would lose the payment-path 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 no output schema, the description does the work of explaining the return value: before/after text, score, task-word coverage, and a JSON merge patch for openapi.json. Combined with pricing and the read-only, open-world nature of the call, an agent has enough to invoke it correctly.

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 description coverage is 100%, so both parameters are already documented, and the baseline applies. The description adds only marginal meaning — 'worst first' ordering and that the score includes task-word coverage tied to the optional task input — without explaining how operations are ranked.

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?

States a specific verb and resource — rewriting operationId, summary, description and tags of up to 5 operations — with clear scope (worst first, from the seller's own listing only). The opening clause 'Same audit, then an open model rewrites...' also distinguishes it from the audit-only sibling without naming it.

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?

The audience and scenario are explicit ('For sellers of paid APIs'), and 'Same audit, then...' implies this call includes the audit so a separate audit step isn't needed. It never names audit_x402_listing as the alternative for read-only diagnosis, so routing between the two is left partly to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources