Multi-DEX Perpetual Futures CLI with MCP integration - provides read-only market data, account information, and trading advisors for Pacifica, Hyperliquid, Lighter, and Aster exchanges
Three tools with READ_ONLY operations. All have descriptions (194-236 chars, baseline 194 avg) and basic input schemas. However, input schemas lack explicit type definitions in several parameters, parameter descriptions are minimal, output schemas are completely undocumented, and error handling is absent. The server demonstrates domain competence (perpetual futures markets) but falls short of production-grade tool definition patterns. Average across three tools: get_markets(60), get_orderbook(62), get_funding_rates(64).
Compare funding rates across all 4 exchanges (Pacifica, Hyperliquid, Lighter, Aster). Returns rates per symbol with spread analysis
Get all available perpetual futures markets on an exchange, including price, funding rate, volume, and max leverage. Works without API keys.
Get the order book (bids and asks) for a symbol on an exchange. Works without API keys.
Output schemas completely undocumented. No field definitions for what get_markets, get_orderbook, or get_funding_rates return. LLMs cannot plan downstream operations or extract required data.
Input parameter 'exchange' lacks enum constraint. Accepts free-form string despite the description listing only four valid values (pacifica, hyperliquid, lighter, aster). LLMs may hallucinate invalid exchange names.
No error handling guidance. Tools provide no recovery instructions for cases like network failure, invalid symbol, or missing market data. Agents receive raw errors with no context for next steps.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | 2026-07-28+ | v2 |
Parameter descriptions are terse (11-62 chars, baseline 72 avg). 'symbol' described as 'Trading pair symbol, e.g. BTC, ETH, SOL' includes example values which LLMs may reuse literally. 'minSpread' lacks range constraints (is it 0-100? 0-1000?).
get_funding_rates 'symbols' parameter accepts array but no guidance on max length, element format, or whether duplicates are handled. What happens if agent passes 100 symbols?