Skip to main content
Glama

x402_listing_check

Checks that a host exposes a valid x402 discovery listing and probes up to 10 listed resources for a real 402 challenge with consistent payTo; never pays.

Instructions

Checks that a host exposes a valid x402 discovery listing (/.well-known/x402, x402.json, x402-listing): JSON, version, https resource URLs, same host, companions (/openapi.json, /llms.txt), and probes up to 10 listed resources for a real 402 challenge with consistent payTo. Never pays. Costs 0.001 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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": {
      "url": "<url>"
    },
    "name": "x402_listing_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesHost or origin URL
probeNoResources to probe, 0-10, default 5

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses probing up to 10 listed resources for a real 402 challenge with consistent payTo, guarantees it never pays, states the cost (0.001 USDC on Base, charged per successful call only), and explains the no-key failure mode returning a 402 challenge. The remaining gap is that it does not say what a passing/failing verdict looks like in the response, which matters since there is no output schema.

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?

It is front-loaded with the core verb and resource, then the validation criteria, then the payment behavior. The dense parenthetical list is efficient rather than padded. Slight density cost, but nearly every clause carries information an agent needs.

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?

For a two-parameter read-only validator with no annotations and no output schema, the definition covers the important unknowns: side effects (it probes remote resources), cost and payment semantics, and the no-key outcome. What is missing is the shape of the success result — an agent cannot tell whether it gets a boolean, a list of failed checks, or per-resource probe results.

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%, so both parameters are already documented, including the 0-10 range and default of 5 for probe. The description adds only marginal meaning — that probing targets listed resources and that the URL is expected to identify a host whose listed resources share that host. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource — validating that a host exposes an x402 discovery listing at /.well-known/x402, x402.json or x402-listing — and enumerates the checks (JSON, version, https URLs, same host, companions). That is far more than a restatement of the name. It stops short of a 5 because it never contrasts itself with the sibling x402_compliance, which an agent might reasonably confuse with this validator.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: this is the tool for verifying a host's x402 discovery document before relying on it. There is no explicit when-to-use/when-not-to-use statement and no named alternative among the x402 siblings (compliance, facilitator_health, manifest_from_openapi). The payment caveat ('Without a payment key this tool returns the 402 challenge') does help an agent predict a failed call, which lifts it above a bare 2.

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