Live crypto prices and market data: spot price, market cap, 24h volume and change for any coins (Bitcoin, Ethereum, Solana, altcoins). Call for any price, market cap or volume question.
| Name | Required | Description | Default |
|---|---|---|---|
| ids | Yes | Coin IDs as lowercase slugs, e.g. ['bitcoin','ethereum','solana'] | |
| vs_currency | No | Quote currency, defaults to 'usd' |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, which cover safety traits. The description adds context on what data is returned (spot price, market cap, etc.) but doesn't disclose response size limits, rate limits, or handling of invalid coin IDs. The description aligns with annotations (no contradiction).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, effectively front-loaded with purpose and examples. The only minor critique is the phrase 'Live crypto prices and market data' slightly redundant with the examples that follow, but overall very concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the output schema exists, the description adequately covers what the tool returns. For a data retrieval tool with 2 parameters, it provides sufficient context. The only gap is lack of guidance on how to handle invalid coin IDs or pagination if many coins are requested.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so baseline is 3. The description adds no additional parameter semantics beyond what the schema provides for ids and vs_currency.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool provides 'live crypto prices and market data' including specific metrics (spot price, market cap, 24h volume and change). It names example coins and explicitly states the use case: 'Call for any price, market cap or volume question.' This fully distinguishes it from siblings like get_crypto_news or get_defi_overview.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides strong contextual guidance by listing when to call (any price/market cap/volume question) and implicitly distinguishes from siblings by focusing on current market data. However, it does not explicitly state when to avoid this tool or mention alternatives like get_market_history for historical data.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct data domain—network health, market prices, news, DeFi, derivatives per-venue vs aggregate, economic calendar, ETH address, whale flows, execution cost, sentiment, implied volatility, macro rates, market brief, dominance, history, and traditional market quotes. The only similar pair (get_derivatives vs get_derivatives_aggregate) is clearly differentiated by level of detail, so there is no real ambiguity.
All tools follow the get_<domain> pattern with descriptive noun phrases (e.g., get_btc_network, get_eth_whale_flows, get_market_brief). No mixed verb styles or casing conventions appear, making the naming fully predictable and consistent.
At 17 tools, the surface is slightly above the ideal 3-15 range, but the breadth of the domain—spot, derivatives, on-chain, macro, sentiment, and execution—justifies each tool. It's borderline but each tool earns its place in a comprehensive market analysis agent.
The toolset covers nearly every major facet of crypto market analysis: prices, history, dominance, derivatives, on-chain activity, DeFi, macro, economic calendar, sentiment, implied volatility, execution cost, and a composite brief. Minor gaps like historical OHLCV or multi-chain on-chain analytics are not critical given the agent's stated focus.