get_bundle_cryptoReturns the top 20 cryptocurrencies by market cap in one call: price, 24h change, 7d change, market cap, and volume. Covers BTC, ETH, SOL, BNB, XRP, USDT, USDC, ADA, AVAX, DOGE, and more. Use this instead of individual get_crypto_price calls when you need broad market coverage. Source: CoinGecko. Price: $0.50 USDC per call via x402 (Base or Solana).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -{
- "$schema": "http://json-schema.org/draft-07/schema#",
- "additionalProperties": false,
- "properties": {
- "as_of": {
- "description": "ISO timestamp of the data fetch",
- "type": "string"
- },
- "bundle": {
- "description": "Bundle identifier: crypto",
- "type": "string"
- },
- "coins": {
- "description": "Top 20 coins by market cap",
- "items": {
- "additionalProperties": false,
- "properties": {
- "change_24h_pct": {
- "description": "24h price change %",
- "type": [
- "number",
- "null"
- ]
- },
- "change_7d_pct": {
- "description": "7d price change %",
- "type": [
- "number",
- "null"
- ]
- },
- "market_cap_usd": {
- "description": "Market cap in USD",
- "type": [
- "number",
- "null"
- ]
- },
- "name": {
- "description": "Full name",
- "type": "string"
- },
- "price_usd": {
- "description": "Current price in USD",
- "type": "number"
- },
- "rank": {
- "description": "Market cap rank",
- "type": "number"
- },
- "symbol": {
- "description": "Ticker symbol",
- "type": "string"
- },
- "volume_24h_usd": {
- "description": "24h volume in USD",
- "type": [
- "number",
- "null"
- ]
- }
- },
- "required": [
- "rank",
- "symbol",
- "name",
- "price_usd",
- "change_24h_pct",
- "change_7d_pct",
- "market_cap_usd",
- "volume_24h_usd"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "count": {
- "description": "Number of coins returned",
- "type": "number"
- }
- },
- "required": [
- "bundle",
- "as_of",
- "count",
- "coins"
- ],
- "type": "object"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations (which already declare readOnly, idempotent, openWorld, non-destructive), the description adds critical behavioral context: the data source (CoinGecko) and the cost/payment mechanism ($0.50 USDC per call via x402 on Base or Solana). This is exactly the kind of operational detail an agent needs before invoking a paid tool.
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?
The description is front-loaded with the core return data, then coverage examples, then usage guidance, then source and pricing. Every sentence earns its place, and the structure supports fast scanning.
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?
With no parameters and no output schema, the description carries the full burden of explaining what is returned. It lists the fields and example assets, states the data source, and discloses the payment model, leaving no significant gap for an agent to call it correctly.
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?
The tool has zero parameters, so the schema requires no parameter documentation. The description correctly does not invent parameter details; the baseline for 0-param tools is 4.
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 states a specific verb and resource ('Returns the top 20 cryptocurrencies by market cap') and enumerates exactly what data is included (price, 24h change, 7d change, market cap, volume). It distinguishes itself from the sibling get_crypto_price by framing itself as a bundle for broad coverage.
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?
It explicitly says 'Use this instead of individual get_crypto_price calls when you need broad market coverage,' naming the alternative and the condition that selects this tool. No further inference is required to choose between the two.
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.