MCP server providing cryptocurrency market data, gas price suggestions, trading information, and market indicators via Desk3 API
The server implements 16 crypto market data tools with basic structure, but has significant gaps in schema completeness, parameter descriptions, and output documentation. All tools are READ_ONLY and make external API calls. Tools have names starting with 'get_' which is good, but descriptions are often terse (10-40 chars, below the 194-char production baseline), and critical schema and output information is missing or undocumented. No tool annotations (readOnlyHint, etc.) are present. Most tools lack parameter type information in visible schemas, and output schemas are not documented. This falls squarely into the 'Fair' (C) to 'Poor' (D) range, workable for simple queries, but missing production-grade documentation and error guidance.
Get the Altcoin Season Index.
Get Bitcoin (BTC) dominance metric.
Get BTC trend chart for the past 3 months.
Get crypto market cycle top indicators.
Get Simple indicators data including Puell Multiple Status, Pi Cycle Top Status, and Crypto Market Cycle Top Indicator.
Get the ETH trend chart for the past three months.
Output schemas completely undocumented. Tools return complex structures (dicts, lists of lists) but LLMs have no guidance on field names, types, or structure. This forces the LLM to guess at response shape and risks parsing failures.
Input parameter descriptions are minimal or missing context. E.g., 'chainid' in get_suggest_gas says 'Chain ID, required' but omits examples (1 for Ethereum, 56 for BSC) or valid range. 'symbol' in crypto tools lacks guidance on format (BTC vs BTCUSDT vs BTC-USDT).
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 46 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 0 | - | v1 |
Get list of fiat currency exchange rates.
Get crypto fear and greed index。
Get economic calendar for specified month. Shows important market or political events.
Get 24-hour mini ticker information.
Get BTC Pi Cycle Top indicator data.
Get Puell Multiple data.
Get Bitcoin Rainbow Price Chart data.
Get EIP1559 estimated gas information.
Get token circulating supply and total supply information.
Get real-time token price information.
No input parameter type definitions visible in provided code. Tools reference 'symbol: str' and 'chainid: str' in Python, but the MCP schema registration is cut off. Without visible JSON Schema types, schema scoring defaulted to low. Verify that tool registration includes proper 'type' and 'description' fields for each parameter.
Tools with no required parameters (get_exchange_rate, get_fear_greed_index, etc.) lack any input schema hint. While optional parameters are valid, the lack of documentation on what each tool retrieves, when to call it, or differences from similar tools (e.g., get_btc_trend vs get_eth_trend) forces the LLM to reason through subtle distinctions.
No error handling guidance. Tools call external APIs (https://mcp.desk3.io/...) but offer no recovery hints if the API is down, rate-limited, or returns malformed data. The RuntimeError messages ('Failed to fetch...') are generic and do not tell the LLM whether to retry, ask the user, or abort.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). While all tools are READ_ONLY, the lack of explicit annotation in the tool definition means clients cannot discover this property and must infer it from the description.
Description brevity. Many tool descriptions are under 50 characters, falling below the production baseline of 194 chars. E.g., 'Get Puell Multiple data.' (23 chars) does not explain what Puell Multiple is, when to use it, or what data is returned. LLMs unfamiliar with crypto metrics will not know why or when to call this tool.
No pagination or result limits documented. Tools like get_mini_24hr and get_cycles may return large datasets, but there is no mention of page size, offset, limit, or cursor parameters. Returning hundreds of items without pagination risks context window exhaustion.
Parameter format ambiguity in crypto symbol handling. Tools accept 'symbol' with format hints in code comments (e.g., 'BTC -> BTCUSDT') but no enum or pattern constraint visible. LLMs may pass invalid formats like 'BTC-USDT' or 'btcusdt' (lowercase), causing API failures without clear guidance.