Skip to main content
Glama
Sign In

Genexxis paid agent tools (x402)

by com.genexxis
OverviewDiscussionsAdmin

prices_token_price

Median spot price of up to 50 coins across Binance, Coinbase, Kraken, OKX and Bybit in usd/usdt/eur/btc, with per-venue prices, 24h change, volume and spread. ids: any CoinGecko id (~23k), ticker, CoinPaprika id or contract address (base:0x..., solana:); DEX-only tokens priced via DefiLlama/DexScreener. Unknown ids: 404, not charged. Price: $0.003 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": {
      "ids": "<ids>"
    },
    "name": "prices_token_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
vsNousd (default), usdt, eur or btc; comma-separated for several (usd,eur)
idsYesComma-separated, max 50: CoinGecko ids (bitcoin,virtual-protocol), tickers (BTC,ETH; any CoinGecko-listed ticker, largest market cap wins), CoinPaprika ids (btc-bitcoin) or contract addresses with chain (base:0x..., ethereum:0x..., solana:<mint>)
chainNoChain for bare 0x addresses: base, ethereum, arbitrum, optimism, polygon, bsc, avalanche (default: base, then ethereum)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ids / description
      Previous value: -"Comma-separated, max 50: CoinGecko ids (bitcoin,virtual-protocol), tickers (BTC,ETH), CoinPaprika ids (btc-bitcoin) or contract addresses with chain (base:0x..., ethereum:0x..., solana:<mint>)"New value: +"Comma-separated, max 50: CoinGecko ids (bitcoin,virtual-protocol), tickers (BTC,ETH; any CoinGecko-listed ticker, largest market cap wins), CoinPaprika ids (btc-bitcoin) or contract addresses with chain (base:0x..., ethereum:0x..., solana:<mint>)"
  2. Changed3 schema fields changed
    • addedInput schema / properties / chain
      Added value: +{
+  "description": "Chain for bare 0x addresses: base, ethereum, arbitrum, optimism, polygon, bsc, avalanche (default: base, then ethereum)",
+  "type": "string"
+}
    • changedInput schema / properties / ids / description
      Previous value: -"Comma-separated CoinGecko ids (bitcoin,ethereum) or tickers (BTC,ETH), max 50"New value: +"Comma-separated, max 50: CoinGecko ids (bitcoin,virtual-protocol), tickers (BTC,ETH), CoinPaprika ids (btc-bitcoin) or contract addresses with chain (base:0x..., ethereum:0x..., solana:<mint>)"
    • changedInput schema / properties / vs / description
      Previous value: -"usd (default), usdt, eur or btc"New value: +"usd (default), usdt, eur or btc; comma-separated for several (usd,eur)"
  3. Added

TDQS

A4.5/5.0
Behavior5/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 so: it names the aggregated venues, the median aggregation method, the ~23k id universe, the DefiLlama/DexScreener fallback for DEX-only tokens, the exact 404/no-charge failure behavior, and the $0.003 USDC x402-on-Base payment model. That is unusually complete disclosure of cost, coverage, and error semantics for an unannotated tool.

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?

Three dense sentences, front-loaded with what is returned and followed by id semantics and pricing. Every clause carries operational information; there is no filler or repetition.

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?

No output schema exists, yet the description enumerates the returned fields (per-venue prices, 24h change, volume, spread) and covers cost, id formats, and error behavior. Nothing an agent needs in order to invoke it correctly and interpret the response appears to be 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?

Schema coverage is 100%, so the schema already documents all three parameters and the baseline would be 3. The description adds a little beyond it — the practical consequence of bad ids (404, not charged) and the fact that DEX-only tokens are resolved through DefiLlama/DexScreener — which changes how an agent chooses id formats rather than merely restating the schema.

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 first clause states a precise verb and resource ('Median spot price of up to 50 coins across Binance, Coinbase, Kraken, OKX and Bybit') and the quote currencies. The cross-venue median framing implicitly but clearly separates it from single-venue or OHLCV-style siblings, so an agent can pick it without opening the schema.

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?

It provides practical calling context — the id formats accepted, the 50-coin cap, DEX-only coverage, and that unknown ids return 404 without charge. However, it never says when this should be preferred over alternatives such as an on-chain price tool, OHLCV history, or the movers tool, so routing guidance is only implied.

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) toolsInspect
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