teardrop

Get Yield Rates

get_yield_rates

Read-only

Get DeFi yield pool rates from DeFiLlama across 1,000+ protocols and all chains: pools sorted by APY with TVL, base/reward APY, and 7d/30d mean APY context, filterable by protocol, chain, min TVL, min/max APY, and symbol. Returns up to 50 pools. For protocol-specific lending comparisons (Aave vs Compound) prefer get_lending_rates.

Use when: Use for broad cross-protocol yield discovery. Call at most once per request — filter with min_apy, max_apy, min_tvl_usd, and symbols_any in a single call, then sort client-side rather than re-calling. For protocol-specific rate questions use get_lending_rates.

Limitations: Third-party DeFiLlama analytics; up to 50 pools per call. The symbol field lists underlying tokens (e.g. 'ETH-USDC') — filter client-side instead of re-calling with different arguments. Reward APY indicates reward-dependent yield; do not present spot APY as durable.

Alternatives: get_lending_rates, get_protocol_tvl, get_token_price

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 13, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only provide readOnlyHint=true; the description adds substantial behavioral context beyond that: third-party DeFiLlama analytics, a hard 50-pool cap, a client-side filtering caveat for the symbol field, and a warning that reward APY is reward-dependent and spot APY should not be presented as durable. This meaningfully exceeds what the annotation conveys.

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 organized into labeled sections (main purpose, Use when, Limitations, Alternatives) that make it scannable and front-loaded. Each sentence earns its place: scope, invocation guidance, caveats, and routing are all distinct and non-redundant, and nothing is wasted.

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?

For a tool with 8 optional parameters, an output schema, and minimal annotations, the description covers purpose, filtering strategy, output limits, symbol-field semantics, and yield-durability caveats. The output schema covers return values, and no material gap remains for an agent to call this correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so all 8 parameters are already documented in the schema; the description adds only marginal parameter-level value (e.g., sorting behavior and the stable_only ranking emphasis). Per the baseline rule for high coverage, 3 is appropriate — the schema carries the semantic load.

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?

Uses a specific verb+resource ('Get DeFi yield pool rates from DeFiLlama') and precisely enumerates what is returned (APY-sorted pools with TVL, base/reward APY, 7d/30d mean APY) and how results can be filtered. It also names get_lending_rates as the protocol-specific sibling, so an agent can immediately distinguish this tool from related ones without opening schemas.

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

Usage Guidelines5/5

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

The 'Use when' section explicitly states the tool is for broad cross-protocol yield discovery, instructs calling at most once per request with filters applied in a single call, and directs protocol-specific questions to get_lending_rates. The Limitations and Alternatives sections reinforce routing, leaving no ambiguity about when to use this tool vs siblings.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.