x402 agent toolkit: service finder, payment safety, Solana & web tools

by dev.workers.moneytools.x402-pay-precheck

Agent tool trends, detailed (paid)

moneytools_trends_detail

Read-onlyIdempotent

Paid ($0.05 USDC on Base via x402 over MCP), read-only, no arguments: MoneyTools detailed agent trends: 30 days per-day tool calls + top tokens queried (aggregate, no personal data). Unpaid calls return the x402 PaymentRequired; retry with params._meta["x402/payment"]. [served by tools.moneytools.dev]

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": "moneytools_trends_detail"
  }
}

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 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, yet the description adds cost ($0.05 USDC on Base via x402), the failure mode on unpaid calls, and a privacy guarantee ('aggregate, no personal data'). That is exactly the kind of operational context 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?

A single front-loaded sentence covers price, safety, argument count, payload, privacy, and error recovery with no filler. It is dense but every clause earns its place; only the bracketed host note is marginal.

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 an output schema present, return values need no explanation, and the description still covers payment, retry mechanics, data scope, and privacy. Nothing an agent needs to invoke this zero-argument paid tool correctly is missing.

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 schema declares zero properties, so the baseline is 4. The description nonetheless reveals that a hidden params._meta["x402/payment"] argument is required on retry, which is meaning the schema does not surface at all.

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 resource and the exact payload: 'MoneyTools detailed agent trends: 30 days per-day tool calls + top tokens queried'. An agent knows precisely what data comes back without opening the output schema.

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 states the invocation context ('no arguments', paid) and gives a concrete recovery path: unpaid calls return PaymentRequired, retry with params._meta["x402/payment"]. It never states when to prefer this over a non-detailed alternative, but no plausible competing sibling is implied.

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

All x402 agent toolkit: service finder, payment safety, Solana & web tools 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?