MoneyTools x402 agent toolkit

x402 market snapshot (paid, read-only)

x402_market_snapshot

Read-onlyIdempotent

Paid ($0.001 USDC on Base via x402 over MCP), read-only, no arguments: snapshot of MoneyTools' live-probed x402 API index — size, live share, endpoints by network and price band, top tags, cheapest live endpoint per top tag, and the most recently verified live endpoints. Unpaid calls return the x402 PaymentRequired; retry with params._meta["x402/payment"].

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond the annotations: annotations only declare readOnly/idempotent/non-destructive, while the description discloses the exact price ($0.001 USDC on Base via x402), the payment transport, and the concrete failure mode (PaymentRequired) with the retry path. This is the key behavioral fact an agent needs, since a naive call will appear to fail.

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-loads the essentials (paid, read-only, no arguments) before the content list, and the payment-retry instruction lands at the end where it is actionable. The middle enumeration is dense and comma-heavy, but each item earns its place by telling the agent what the payload contains.

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?

An output schema exists so return values need not be spelled out, and the description covers cost, auth/payment mechanics, and failure recovery — the parts a schema cannot express. Minor gaps: nothing about data freshness/latency of the "live-probed" index, and no pointer to the sibling to use for narrower lookups.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The declared schema is an empty object, yet the description reveals a real pseudo-parameter the schema omits entirely — params._meta["x402/payment"] — and explains when it must be supplied. That is meaningful semantics added on top of an empty schema, not repetition.

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 and resource ("snapshot of MoneyTools' live-probed x402 API index") and enumerates the exact contents — size, live share, endpoints by network/price band, top tags, cheapest live endpoint per tag, recent verified endpoints. An agent knows precisely what it gets. It never names or contrasts the nearby x402_find_endpoint / x402_recommend / x402_quote_compare siblings, so differentiation is inferred from the aggregate nature of the snapshot rather than stated.

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

Usage Guidelines3/5

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

Usage context is implied through the enumerated content (a market-overview call) plus the hard operational precondition that unpaid calls fail with PaymentRequired and must be retried with params._meta["x402/payment"]. There is no explicit when-to-use-this-instead-of that sibling guidance and no stated exclusion, so the agent must infer that this is the broad overview rather than a targeted lookup.

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

All MoneyTools x402 agent toolkit 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?