Skip to main content
Glama

zato crypto data

x402 preflight: check an endpoint, its payTo wallet and the domain declaration before paying

preflight
Read-only

Right before paying an x402 URL: decodes its 402 terms, checks the payTo wallet and whether the domain declares it. Never pays. Price: $0.003 USDC per call (x402, Base).

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

Input Schema

NameRequiredDescriptionDefault
urlYesx402 endpoint URL (https)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds meaningful behavior by stating 'Never pays' and disclosing the per-call price. It does not cover return structure or rate limits, but it adds important cost and safety context.

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?

The definition is compact and front-loaded: timing first, then what is checked, then safety and cost. Every sentence carries actionable information.

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 one-parameter composite check with no output schema, the description is largely complete: it covers intent, checks performed, non-payment behavior, and cost. It could say more about the shape of the result, but nothing critical for invocation is missing.

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 the single url parameter is already well documented. The description confirms the URL is an x402 endpoint but adds no syntax or validation details beyond the schema baseline.

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 precise pre-payment verb and resource: it decodes an x402 URL's 402 terms, checks the payTo wallet, and checks domain declaration. This composite scope is specific enough for an agent to distinguish it from narrower sibling checks such as payto_check.

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 phrase 'Right before paying an x402 URL' clearly establishes when to use the tool. It does not explicitly name alternatives or exclusions, but the timing and composite scope imply intended use clearly.

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