Skip to main content
Glama

x402_preflight__check

Validate a public x402 endpoint's 402 challenge before paying it: scheme, network, USDC asset, payTo shape, price, latency, openapi presence. 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/x402-preflight/check

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x402_preflight__check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / url / description
      Removed value: -"https URL of the x402 endpoint"
    • removedInput schema / required
      Removed value: -[
      -  "url"
      -]
  2. Changed2 schema fields changed
    • addedInput schema / properties / url / description
      Added value: +"https URL of the x402 endpoint"
    • addedInput schema / required
      Added value: +[
      +  "url"
      +]
  3. Changed2 schema fields changed
    • removedInput schema / properties / url / description
      Removed value: -"Public https endpoint to inspect for an x402 payment challenge"
    • removedInput schema / required
      Removed value: -[
      -  "url"
      -]
  4. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"public https URL of the x402 endpoint to audit"New value: +"Public https endpoint to inspect for an x402 payment challenge"
  5. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"https URL of an x402-paid endpoint to probe"New value: +"public https URL of the x402 endpoint to audit"
  6. First observed

TDQS

A3.9/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 meaningful work: it discloses that each call costs $0.01 in USDC on Base (eip155:8453), that payment goes in params._meta["x402/payment"], and that transport is HTTP GET. It does not cover failure behavior, rate limits, or whether the validated response is cached.

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 purpose, then the enumerated checks, then cost and transport in a compact two-part block. It is dense and nearly every clause carries information, though the run-on enumeration makes it slightly harder to scan.

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 validation tool, the description covers the input subject, the checks performed, the price, and the invocation channel, which effectively implies the shape of the result. With no output schema, a brief note on what a passing versus failing result looks like would have closed the remaining gap.

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 0% and the single url parameter is not even required, yet the description only implies that url is the public x402 endpoint being checked. It adds no format detail (full URL versus base host, scheme requirements) and never explains the out-of-schema payment-injection parameter's shape.

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?

States a specific verb (validate) and resource (an x402 endpoint's 402 challenge) and enumerates exactly what is checked: scheme, network, USDC asset, payTo shape, price, latency, openapi presence. It never distinguishes itself from similarly named siblings such as x402check__check, so it stops short of a 5.

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?

"before paying it" gives a clear trigger condition for when to call the tool. It stops short of naming any alternative or stating when not to use it, so there is no explicit 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