Skip to main content
Glama
Sign In

47620 Multichain Data API — onchain, crypto, utilities, x402 stats

by xyz.47620
OverviewDiscussionsAdmin

crypto_price

Live crypto spot price in USD for a coin (btc, eth, sol, bnb, xrp, ada, doge, avax, link, matic, arb, op): price + 24h change, high, low and quote volume. -> /x/crypto/price/:symbol. Pay-per-call ($0.002 USDC).

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

Input Schema

NameRequiredDescriptionDefault
symbolYesCoin ticker or name, e.g. btc, eth, sol

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It importantly discloses the pay-per-call cost ($0.002 USDC) and the endpoint path, which are real behavioral traits beyond the schema. However, it omits rate limits, error/unsupported-symbol behavior, and caching/freshness guarantees.

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 dense sentence front-loads the core purpose (live spot price + returned metrics) before the endpoint and cost. No filler sentences, though the run-on structure packs endpoint and pricing into the same block.

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?

With no output schema and no annotations, the description compensates by naming the returned fields (price, 24h change, high, low, quote volume) and the cost model. It covers what an agent needs to call and interpret the tool, missing only edge-case/error behavior.

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% and there is a single required param, so baseline is 3. The description adds value by enumerating the concrete supported symbols (btc, eth, sol, bnb, ...) which the schema only illustrates with 'e.g. btc, eth, sol', effectively documenting the accepted input domain.

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+scope: live spot price in USD for a named coin, and even enumerates the supported tickers and the returned fields. It is clearly a spot-price lookup, distinguishable from crypto_ohlcv/crypto_indicators by naming the resource, though it does not explicitly contrast itself with those siblings.

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 (fetch a spot price for a supported coin) but there is no explicit when-to-use vs alternatives guidance, e.g. no pointer to crypto_ohlcv for historical bars or to token/token_report for metadata. The pay-per-call note gives a cost signal but not a routing rule.

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

All 47620 Multichain Data API — onchain, crypto, utilities, x402 stats 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