Best DeFi yields ranked by APY -- lending, staking, LP across 100+ protocols. Powered by DeFiLlama.
Single tool 'defi_find_best_yields' has a well-structured schema with 4 parameters (token required, chain/minTvl/limit optional), all with type definitions and descriptions. Description is comprehensive (380+ chars) and includes usage guidance, examples, and anti-patterns (what NOT to use it for). However, the description violates the rubric by embedding example values ('USDC', 'ETH', 'WBTC', 'base', 'ethereum') which LLMs tend to reuse literally. Output schema is documented in the description (pool, protocol, chain, apy, tvl, riskLevel, type fields) but not formally in JSON Schema. Parameter descriptions are adequate but could be more precise on constraints (e.g., minTvl default 100000 is stated but max limit of 50 is buried in description). No enum constraints on 'chain' parameter despite finite valid values. Overall solid for a single-tool server but lacks formal output schema and has minor description anti-patterns.
Use this when you need to find the best DeFi yields for a token across all chains and protocols. Returns ranked opportunities in JSON. 1. pool: pool/vault name and pair 2. protocol: protocol name (Aave, Compound, Lido, Aerodrome, etc.) 3. chain: which blockchain network 4. apy: current annual percentage yield 5. tvl: total value locked in USD 6. riskLevel: risk assessment (low/medium/high) 7. type: yield type (lending, staking, LP, vault) Example output: {"pools":[{"pool":"USDC Lending","protocol":"Aave V3","chain":"base","apy":4.82,"tvl":125000000,"riskLevel":"low","type":"lending"}],"token":"USDC","totalPools":15} Use this BEFORE deploying idle capital to find the highest safe yield. Essential for yield optimization and DeFi strategy comparison. Do NOT use for swap quotes -- use dex_get_swap_quote instead. Do NOT use for wallet balance -- use wallet_get_portfolio instead. Do NOT use for Base-only yields -- use base_get_defi_opportunities instead. Do NOT use for liquidation risk -- use defi_get_liquidation_levels instead.
Example values embedded in parameter descriptions ('USDC', 'ETH', 'WBTC', 'base', 'ethereum'), LLMs reuse these literally instead of adapting to context
Output schema documented only in description text, not as formal JSON Schema, LLMs cannot parse structure programmatically
'chain' parameter accepts free-form strings instead of enum, invites hallucinated chain names like 'solana' or 'cosmos' if not in supported set
No tool annotations (readOnlyHint, idempotentHint) despite tool being read-only and idempotent, misses protocol capability
Error handling guidance missing, no recovery hints if token not found, chain unsupported, or API fails
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 64 | 2025-06-18+ | v2 |