SiteCheck Crypto & Finance

CoinGecko spot prices for up to 10 coins in one currency

finance_coingecko

Read-only

CoinGecko spot prices for up to 10 coins (by CoinGecko id, e.g. bitcoin,ethereum) in one currency, with 24h change. Prices are CoinGecko's aggregated spot prices; no history. Related tools on this server, for a different need: finance_bstock when you need B-Stock wholesale liquidation auctions: total live lots; finance_coinmarketcap when you need CoinMarketCap ranked crypto listing: name, symbol, USD. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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

Input Schema

Name	Required	Description	Default
`vs`	No	Quote currency code, e.g. usd, eur (default usd)
`ids`	Yes	Comma-separated CoinGecko ids, up to 10 (e.g. bitcoin,ethereum)

Output Schema

Name	Required	Description	Default
`vs`	No
`coins`	No
`source`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only provide readOnly/openWorld hints. The description adds material operational details: aggregated spot prices with no history, $0.002 per successful call paid via x402 on Base/Solana/Arc, and failed calls are not charged.

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?

The purpose is front-loaded, followed by pricing and sibling routing. Some phrasing is slightly clunky, but every element carries useful selection or operational information.

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 and read-only/open-world annotations already present, the description supplies the remaining critical context: aggregation scope, no history, payment model, and no charge for failures. Nothing essential for correct invocation 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?

Schema coverage is 100%, so the schema already documents both parameters. The description reinforces semantics by specifying up to 10 CoinGecko ids, an example format, one quote currency, and 24h change output.

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?

States a specific verb/resource and scope: CoinGecko spot prices for up to 10 coins in one currency with 24h change. It explicitly positions the tool against finance_bstock and finance_coinmarketcap, so an agent can distinguish the intended use.

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?

Names two alternatives with conditions ('when you need...'), giving explicit routing guidance for those cases. It does not exclude other spot-price siblings such as finance_binance_prices or finance_coinbase_exchange_products, so the guidance is clear but not exhaustive.

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

All SiteCheck Crypto & Finance 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?