Skip to main content
Glama

Thread Kit: posts that fit every network

Audit your x402 / MPP paid API listing: will agents find it, see the price and complete a paid call? ($0.040)

audit_x402_listing
Read-onlyIdempotent

For sellers of paid APIs. Reads the public listing of the origin you name (openapi.json, /.well-known/x402, llms.txt, up to 3 unpaid calls that should answer 402) and returns a 0-100 score, ranked fixes with the reason each one costs sales, per-operation issues (missing schemas, generic operationIds, required inputs without examples that make blind paid calls fail) and 402 checks (400 before 402, payTo checksum, network names, price mismatch, bazaar metadata). Optional task = what buyers ask for. Deterministic; origin "sample" audits a built-in example. An origin that does not answer is not charged. PAID: $0.040 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": "audit_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?

Annotations already declare readOnly, idempotent, open-world, non-destructive, but the description adds substantial context beyond that: the cost ($0.040 per call in USDC on Base), the two billing paths (x402 over MCP vs prepaid credits via Authorization: Bearer tkc_... header), the rule that a non-responding origin is not charged, and the fact that results are deterministic. For a paid tool, pricing and billing behavior are exactly what an agent needs before invoking.

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?

Content is front-loaded with audience, then what is read, then what is returned, then payment terms. However, the core is delivered as one very long run-on sentence with parenthetical lists, which is dense; splitting the return-value inventory from the probing behavior would read better. Little is wasted, but readability suffers.

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 only two parameters, no output schema, and read-only annotations, the description still fully covers what an agent needs: inputs accepted, what gets probed, the shape of the result (score, fixes with reasons, per-operation issues, 402 checks), determinism, and cost/payment mechanics. Nothing material is missing for correct invocation.

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% and the schema already explains both the task parameter (what a buyer would ask, max 160 chars) and origin (host, path-probing, 'sample' for a built-in listing). The description mostly restates these points ('Optional task = what buyers ask for', 'origin "sample" audits a built-in example') rather than adding new syntax or edge-case meaning, so the baseline 3 applies.

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 verb (audit) and a precise resource (an x402/MPP paid API listing), then spells out exactly what is fetched (openapi.json, /.well-known/x402, llms.txt, up to three unpaid 402 probes) and what comes back (0-100 score, ranked fixes, per-operation issues, 402 checks). This is clearly distinguishable from siblings like rewrite_x402_listing or payment_options.

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 opening 'For sellers of paid APIs' sets the audience, and the optional task parameter's purpose (what buyers ask for) is stated. It also routes agents to payment_options for the Bearer-credit configuration. It never explicitly says when not to use this tool or names rewrite_x402_listing as the follow-up for applying fixes, so it stops short of full routing guidance.

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