Genexxis paid agent tools (x402)

prices_ohlcv

Spot OHLCV candles (1m to 1w, up to 1000) for a coin against USDT from Binance (fallback OKX), with window open/high/low/close, change % and exact traded VWAP. Price: $0.005 USDC per call, paid with x402 on Base.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "prices_ohlcv"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Number of candles, 1-1000 (default 100)
`symbol`	Yes	Coin ticker, e.g. BTC, ETH, SOL
`interval`	No	1m, 5m, 15m, 30m, 1h (default), 4h, 1d, 1w

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 notably well: it discloses the paid-access model ($0.005 USDC per call via x402 on Base), the upstream source with a fallback provider, and hard bounds on intervals and candle count. It omits rate limits, failure/retry behavior, and whether data is delayed, which keeps it short of a 5.

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 with zero filler: resource and bounds first, returned fields next, commercial terms last. Nothing is repeated for its own sake and the most decision-relevant facts come first.

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?

There is no output schema, yet the description enumerates the returned fields (open/high/low/close, change %, VWAP), which is exactly what the agent needs to trust the payload. For a 3-parameter read tool the remaining gap — no mention of response shape beyond field names or error behavior — is minor.

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 description coverage is 100%, so all three parameters are already documented. The description adds only a small amount — that the series is quoted against USDT, clarifying what `symbol` refers to, and restating the interval/limit ranges. Baseline 3 applies when the schema does the heavy lifting.

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?

The description names a specific resource (spot OHLCV candles), its quote currency (USDT), and its upstream sources (Binance with OKX fallback), which is far more than a restated name. It does not distinguish itself from the closely related siblings prices_token_price or prices_movers, so an agent must infer when candles beat a spot quote.

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 is implied by the resource itself — you fetch candles when you need historical bars — but there is no explicit when-to-use/when-not guidance and no pointer to the sibling tools that cover spot price or movers. The agent is left to infer the routing decision.

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?