Skip to main content
Glama

x402check__receipt

Preflight an x402 endpoint before you pay it: reachable, valid 402 terms, payTo OFAC-screened, domain age. Verdict + problem list. Bundle report screens company, domain and endpoint in one call. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/x402check/receipt

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": "x402check__receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttps URL of the x402 endpoint to preflight

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description does real work: it states the price ($0.01 per call in USDC on Base, eip155:8453), exactly where payment goes (params._meta["x402/payment"]), and the transport (HTTP GET to the given URL). It does not say what happens if the endpoint fails validation after payment is submitted, nor whether calls are cacheable/idempotent, which matters for an agent deciding whether to retry.

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 purpose and checks, then the cost/payment facts, then the endpoint. Dense but nearly every clause carries decision-relevant information. The raw HTTP URL is slightly out of register for an MCP tool, but it does serve as the invocation target for the paid call.

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?

For a one-parameter tool with no output schema, the description covers what it checks, what it returns in shape (verdict + problem list), what it costs, how payment is attached, and which sibling to prefer for broader coverage. Nothing an agent needs in order to call it correctly is absent.

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?

The single schema parameter is 100% documented, so the baseline would be 3. The description goes beyond it by documenting an off-schema input the caller must supply: the x402 payment envelope in params._meta["x402/payment"] with its chain and currency. That is genuinely non-obvious information an agent could not get from the schema.

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?

"Preflight an x402 endpoint before you pay it" gives a specific verb and resource, and the four checks (reachable, valid 402 terms, OFAC-screened payTo, domain age) plus "Verdict + problem list" make the output concrete. It also names a sibling differentiator ("Bundle report screens company, domain and endpoint in one call"). The only friction is that the tool name "receipt" implies fetch-a-receipt while the description describes a preflight diagnostic, which the text never reconciles.

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 timing condition is explicit: "before you pay it", and the bundle alternative is described with its distinguishing scope (company + domain + endpoint in one call). What's missing is a pointer for the more granular single-purpose siblings (check/guard/screen) so the agent can tell whether this broad preflight is overkill for a simple liveness check.

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