Genexxis paid agent tools (x402)

prices_movers

Top 24h gainers and losers among Binance spot USDT pairs above a minimum 24h USD volume (default 10M), with price, change % and volume, plus market breadth. Price: $0.003 USDC per call, paid with x402 on Base.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Coins per side, 1-50 (default 10)
`minVolumeUsd`	No	Minimum 24h quote volume in USD (default 10000000)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses a paid, metered call ($0.003 USDC per call via x402 on Base), the default volume floor, and the shape of the result including market breadth. It does not state rate limits, caching, or whether the response is a single snapshot versus streaming.

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?

Two dense sentences: the operation and its scope come first, the payment terms last. No filler, no repetition of the tool name.

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?

For a two-parameter read tool with a fully documented schema and no output schema, this covers what is computed, what is returned, and the cost of the call. The only meaningful omission is ordering/pagination behavior for the limit parameter beyond 'coins per side'.

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 both parameters (limit, minVolumeUsd) are documented there with defaults and ranges. The description only restates the default volume threshold and 'top' semantics, adding little beyond the schema — baseline 3.

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/resource: top 24h gainers and losers, scoped to Binance spot USDT pairs above a volume threshold, and enumerates returned fields. The spot-pair scoping implicitly separates it from perps-oriented siblings like perps_extremes, but no sibling is named explicitly.

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?

The scope (spot USDT pairs, volume floor) implies when it is appropriate, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative such as prices_ohlcv or perps_extremes.

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

All Genexxis paid agent tools (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?