Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

Check X402 Hub Health

x402_check_health
Read-onlyIdempotent

Probe live readiness of the Stripe X402 Agent Payment Hub and verify connectivity to its backing Stripe credit ledger. Use this before starting an autonomous workflow or when diagnosing 503 errors; do not use it to browse capability rates (use x402_list_capabilities) or read an account balance (use x402_get_account). Requires no authentication, incurs no charge, and returns ok=false (HTTP 503) if the backing credit ledger is unreachable.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
okYesTrue when both the Payment Hub and Stripe credit ledger are healthy.
schemaNoHealth schema identifier (atlas.x402.center_health.v1).
checked_atNoUTC ISO-8601 timestamp when readiness was verified.
stripe_credit_ledgerNo
paid_capabilities_countNoCount of active priced HTTP 402 capabilities served by the hub.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that no authentication is required, no charge is incurred, and that failure surfaces as ok=false / HTTP 503 when the backing credit ledger is unreachable — none of which readOnlyHint/idempotentHint convey. The remaining gap is timing behavior: for a probe, expectation about latency or timeout before the agent concludes the hub is down is not stated.

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?

Three sentences, front-loaded with the purpose, then routing guidance, then cost/auth/failure facts. Every clause carries information the agent would otherwise have to guess, and there is no filler or restatement of the name.

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 zero-parameter, read-only probe with full annotation coverage and an output schema, the description supplies exactly the missing pieces: safety-relevant cost/auth facts and the failure signal. Return-value detail is correctly left to the output schema.

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 tool takes zero parameters, so the baseline is 4 and there is no parameter meaning for the description to add. The description correctly avoids restating an empty schema and instead spends its words on invocation context.

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?

Uses a specific verb phrase ('Probe live readiness of the Stripe X402 Agent Payment Hub') plus a second check ('verify connectivity to its backing Stripe credit ledger'), so the agent knows exactly what is being tested. It also explicitly differentiates itself from x402_list_capabilities and x402_get_account, which could otherwise be confused with a hub-status call.

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

Usage Guidelines5/5

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

Gives both a positive trigger ('before starting an autonomous workflow or when diagnosing 503 errors') and explicit exclusions with the correct sibling named for each ('do not use it to browse capability rates... or read an account balance...'). Nothing about when to select this tool is left to inference.

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