Lucky x402

x402 ping

x402-ping

Read-onlyIdempotent

x402 payment-flow test: the cheapest real paid call ($0.001 USDC) to verify an agent's wallet/client end-to-end before wiring paid tools. Returns server time and echoes your JSON; the settlement tx comes back in X-Payment-Response (REST) or _meta (MCP). No data, no account Price: $0.001 per call, USDC on Base via x402.

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

Input Schema

Name	Required	Description	Default
`echo`	No	optional: any JSON value to echo back (<= 500 bytes)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive/openWorld), the description discloses the concrete cost and chain ($0.001 USDC on Base via x402), what the call returns (server time plus echoed JSON), and where the settlement tx appears (X-Payment-Response for REST, _meta for MCP). That is exactly the payment-mechanics context an agent needs and the annotations cannot express.

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?

It is dense and front-loaded with the purpose, but it is a single run-on paragraph with a punctuation break ('No data, no account Price: $0.001 per call') and the $0.001 price is stated twice. Minor redundancy and cleanup would make it tighter.

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?

With no output schema, the description carries the return-value burden and does so: server time, echoed JSON, and the settlement tx location per transport. Cost, chain, and payment protocol are all specified, leaving nothing an agent needs missing before calling.

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 100% and the single optional 'echo' parameter is fully documented in the schema (any JSON value, <= 500 bytes). The description only restates 'echoes your JSON' without adding format or size guidance, so the baseline 3 applies.

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 specific action (a paid x402 ping/test call) and its scope: 'the cheapest real paid call ($0.001 USDC) to verify an agent's wallet/client end-to-end.' The phrase 'No data, no account' explicitly separates it from the data-returning siblings like wallet-status or token-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?

It gives a clear when-to-use: run this before wiring paid tools to verify wallet/client plumbing end-to-end. There is no explicit when-not or named alternative, but 'No data, no account' implicitly rules out using it as a data source, which covers the main misuse risk.

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

All Lucky x402 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?