Solana DEX pool liquidity depth -- TVL, slippage at 1/2/5%, volume, fee tier. Raydium, Orca, Meteora.
Single tool 'solana_scan_pool_liquidity' has a well-structured input schema with proper type definitions and a clear mint parameter description. The tool description is comprehensive (450+ chars), explaining what it does, when to use it, and what it returns with concrete examples. However, the description embeds example output values (e.g., 'So11111111111111111111111111111111111111112 for SOL'), which LLMs may reuse literally. Output schema is documented in the description but not formally declared in a separate schema field. Error handling and recovery guidance are absent. The tool follows verb_noun naming (solana_scan_pool_liquidity) and has appropriate READ_ONLY risk classification.
Use this when you need to check liquidity depth of a Solana DEX pool before trading. Returns TVL, slippage estimates, volume, and fee tier for pools matching a token mint. 1. pools: array of DEX pools for the given token 2. Each pool contains: dex (Raydium/Orca/Meteora), pairName, tvlUsd, volume24h, feeTier, poolAge 3. depth: slippage estimates at 1%, 2%, 5% trade sizes in USD 4. bestPool: the pool with deepest liquidity 5. totalTvl: combined TVL across all pools for this token Example output: {"pools":[{"dex":"Raydium","pairName":"SOL/USDC","tvlUsd":45000000,"volume24h":12000000,"feeTier":0.25,"poolAge":"342d"}],"depth":{"1pct":500000,"2pct":950000,"5pct":2100000},"bestPool":"Raydium SOL/USDC","totalTvl":62000000} Use this BEFORE executing large swaps to estimate slippage. Essential for position sizing, liquidity analysis, and avoiding thin pools. Do NOT use for swap quotes -- use jupiter_get_swap_quote. Do NOT use for new token launches -- use solana_scan_new_tokens. Do NOT use for Solana fees -- use solana_get_priority_fees.
Output schema not formally declared. Description includes example output but no structured schema definition for response fields (pools, depth, bestPool, totalTvl). LLMs cannot reliably extract or chain results without a formal output schema.
Example values embedded in description (mint address 'So11111111111111111111111111111111111111112'). LLMs tend to reuse example values literally rather than adapting to context, risking invalid calls.
No error handling or recovery guidance. If a mint is invalid or no pools exist, the tool provides no actionable error message or next steps for the LLM.
No pagination or result limits documented. If a token has hundreds of pools, the response could be massive and exhaust context. No limit parameter or guidance on capping results.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 67 | 2025-06-18+ | v2 |
Tool description includes cross-references to other tools (jupiter_get_swap_quote, solana_scan_new_tokens, solana_get_priority_fees) that are not defined in this server. These external tool assumptions are not validated and may confuse agents.