Skip to main content
Glama

x402_facilitator_health

Checks x402 facilitator health by calling GET /supported to report alive status, auth requirements, latency, supported schemes and networks, and deprecated URLs.

Instructions

x402 facilitator health check: calls GET /supported on a facilitator (or on a default list incl. CDP, xpay, x402.org, PayAI), reports alive/auth-required, latency, supported kinds (version, scheme, network), V2 and network support, and flags deprecated URLs. Costs 0.001 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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_facilitator_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoFacilitator base URL (optional)
networkNoCAIP-2 network to check, default eip155:8453

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the HTTP call made (GET /supported), the per-call price (0.001 USDC on Base, charged only on success), and the exact failure mode without a payment key (402 challenge returned rather than an error). That is meaningful operational context an agent cannot get from structured fields. It does not cover retry/timeout behaviour or what latency figures mean, so not a 5.

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?

The purpose is front-loaded in the first clause, and every subsequent clause adds new information: inputs, outputs, price, and failure mode. The wording is dense but not padded. Minor cost: 'V2 and network support' is vague enough that it doesn't fully land, and the payment note is tacked on rather than integrated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must describe returns — and it does list what the report contains (alive/auth-required status, latency, supported kinds with version/scheme/network, V2 support, deprecated-URL flags). Combined with the cost and 402 disclosure, the agent can call it safely. What is missing is the practical shape of the response (structure of the result, whether the default list is returned as an array) and how multiple facilitators are keyed, which leaves an agent guessing at how to read results.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: omitting 'url' triggers a check across a named default facilitator list (CDP, xpay, x402.org, PayAI) rather than simply doing nothing, and 'network' defaults to Base (eip155:8453). It adds little on url format (base URL vs full endpoint), so a 4 rather than 5.

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?

Names a specific verb and resource ('health check' of an 'x402 facilitator') and pins down the exact mechanism ('calls GET /supported'). It also states the scope precisely: one named facilitator or a built-in default list of CDP, xpay, x402.org and PayAI. An agent can tell at a glance this is a facilitator liveness/probe tool, not a transaction or listing tool like the neighbouring x402_* entries.

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 description makes the calling convention clear: pass a url to probe a specific facilitator, or omit it to sweep the default list, and network selects the CAIP-2 chain. It also states a hard prerequisite — a payment key is required or the call returns a 402 challenge — which is exactly the kind of condition an agent needs before invoking. It stops short of explicit when-not-to-use guidance or naming an alternative sibling for facilitator-related tasks.

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