Teardrop

Get Yield Rates

get_yield_rates

Read-only

Get DeFi yield pool rates from DeFiLlama, covering 1,000+ protocols across all chains. Returns pools sorted by APY with TVL, base rate, reward APY, and 7d/30d mean APY context. Filter by protocol (e.g. 'aave-v3', 'compound-v3'), chain (e.g. 'Ethereum', 'Base'), minimum TVL, and minimum APY. Use this to answer questions like 'Where can I get the best USDC yield?', 'What is Aave's current APY on Ethereum?', or 'Compare Aave vs Compound yields'. Returns up to 50 pools. Call once per query unless a genuinely disjoint filter is required. The returned symbol field contains the underlying tokens (e.g. 'USDC', 'ETH-USDC', 'WBTC'); filter on the client side by inspecting symbol rather than re-calling with different arguments. Use min_apy, max_apy, min_tvl_usd, and symbols_any to prune noise in a single call. symbols_any matches whole symbol tokens (e.g. 'USDC' matches 'USDC' and 'ETH-USDC' but not 'TULIPAUSDC') and returns the highest-ranked pools for EACH requested symbol, so one call gives a complete per-symbol comparison; symbols with no matching pool are named in note. Set max_apy (e.g. 30) to exclude leveraged/boosted pools so genuine yields surface. Set stable_only=true when you need consistent stablecoin yield screening; this ranks by 30d mean APY first and still returns spot/base/reward components.

Input Schema

TableJSON Schema

Name	Required	Description
`chain`	No	Filter by chain name (e.g. 'Ethereum', 'Base', 'Arbitrum'). Case-insensitive. None = all chains.
`limit`	No	Maximum number of pools to return, sorted by APY descending.
`max_apy`	No	Exclude pools with APY above this value (%). Default None = no upper bound. Use to filter out leveraged/boosted pools (e.g. max_apy=30) so genuine stablecoin yields surface.
`min_apy`	No	Exclude pools with APY below this value (%). Default 0 includes all.
`protocols`	No	Filter by DeFiLlama project slugs (e.g. ['aave-v3', 'compound-v3']). None or empty list = include all protocols.
`min_tvl_usd`	No	Exclude pools with TVL below this threshold (USD). Default $1M filters noise.
`stable_only`	No	When true, return only stablecoin pools and rank by 30d mean APY first to emphasize consistency over short-term spikes.
`symbols_any`	No	Optional symbol filter. If provided, include pools whose symbol field contains at least one token from this list (case-insensitive). Use held token symbols from get_wallet_portfolio to focus results.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	Yes
`pools`	Yes
`provenance`	No	Source and freshness metadata for the DeFiLlama response.
`total_matching`	Yes
`filters_applied`	Yes

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds rich behavioral detail beyond the readOnlyHint annotation: describes return fields, the 50-pool cap, symbols_any whole-token matching and per-symbol ranking, the note field for unmatched symbols, and the effect of stable_only and max_apy on ranking and filtering. This gives the agent a strong mental model of the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with a clear purpose, then provides dense, high-value guidance on filtering and edge cases. It is longer than average, but every sentence adds information relevant to using the tool correctly, and it maintains a logical flow from what it does to how to use specific parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 8 optional parameters, an output schema, and only a readOnlyHint annotation, the description fully compensates: it covers use cases, parameter interpretation, edge-case behavior, and client-side filtering instructions. The tool's behavior is thoroughly specified, leaving no significant ambiguity for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though the schema already covers all parameters, the description adds meaning beyond schema entries: it explains that symbols_any returns the highest-ranked pool per requested symbol and notes missing symbols in the note field, clarifies stable_only's ranking change, and recommends max_apy=30 to exclude leveraged pools. These details are not in the schema and materially improve parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool gets DeFi yield pool rates from DeFiLlama, covers 1,000+ protocols across chains, and returns pools sorted by APY with specific fields. It includes example queries that make the purpose and scope unambiguous, and its focus on yield rates with protocol/chain filters distinguishes it from sibling tools like get_lending_rates and get_defi_positions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use guidance via example questions and specific strategies like 'Call once per query unless a genuinely disjoint filter is required' and 'filter on the client side by inspecting symbol rather than re-calling'. However, it does not explicitly name alternatives or state when not to use this tool in favor of a sibling, so it falls short of a perfect 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Teardrop tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Most tools target distinct blockchain/DeFi resources and actions. A few pairs like get_lending_rates vs get_yield_rates and get_defi_positions vs get_liquidation_risk have overlapping boundaries, but detailed descriptions and explicit redundancy notes (e.g., get_eth_balance vs get_wallet_portfolio) reduce confusion.

Naming Consistency5/5

All tools follow a consistent snake_case verb_noun pattern (e.g., get_block, convert_currency, decode_transaction). The only minor deviations are noun-first names like http_fetch and web_search, but the style is uniform and predictable.

Tool Count2/5

At 27 tools, the server exceeds the 25-tool threshold for 'too many' and feels heavy. While the breadth of DeFi and crypto features justifies some size, the number is unwieldy for an agent to scan efficiently and could be consolidated (e.g., merging balance-related tools).

Completeness4/5

The tool surface covers a wide range of blockchain data: balances, prices, TVL, yields, DEX quotes, gas, block/transaction details, approvals, and DeFi positions. Gaps include lack of wallet transaction history and NFT support, but these are beyond the server's clear focus on read-only DeFi analytics.

Resources

Need Help?