Skip to main content
Glama

List DeFi yield pools by APY from DefiLlama

defi_yields
Read-only

DeFi yield pools from DefiLlama with at least $1M TVL, sorted by APY and filtered by chain, project or symbol (max 50). APY is DefiLlama's estimate, split into base and reward; reward APYs are often temporary. Attribution: Data: DefiLlama. Information only, not financial advice. Related tools on this server, for a different need: defi_chains when you need total value locked by chain from DefiLlama, largest first; defi_stablecoins when you need to list stablecoins with supply and peg from DefiLlama. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "defi_yields"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain name, e.g. base
limitNo1 to 50 (default 20)
symbolNoPool symbol, e.g. USDC
projectNoProtocol name contains, e.g. aave
minTvlUsdNoMinimum TVL in USD (default and floor 1,000,000)

Output Schema

NameRequiredDescriptionDefault
noteNo
countNo
poolsNo
sourceNo
checkedAtNo
minTvlUsdNo
disclaimerNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses the minimum TVL floor, maximum result count, APY composition (base vs reward) with a caveat that reward APYs are often temporary, and a per-call pricing model including that failed calls are not charged. These are material behavioral traits an agent should know before calling.

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

Conciseness4/5

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

The core selection information is front-loaded and the description is generally efficient. It includes necessary pricing and caveat information, though the attribution and not-financial-advice sentences are less essential for tool invocation and slightly lengthen the definition.

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?

Given the presence of an output schema and the read-only/open-world annotations, the description provides enough context for correct selection and invocation: data source, filters, sorting, result cap, TVL floor, cost model, and alternative tools. Nothing critical appears to be missing.

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 the schema already documents chain, limit, symbol, project, and minTvlUsd. The description adds some useful context about sorting by APY and the $1M TVL floor, but most filter details repeat the schema rather than adding new parameter-level meaning.

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 states a specific resource (DeFi yield pools from DefiLlama), scope (at least $1M TVL, sorted by APY, max 50), and filter dimensions (chain, project, symbol). It also explicitly distinguishes itself from defi_chains and defi_stablecoins, so an agent can identify the tool without opening sibling 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 description explicitly routes the agent to alternatives with conditions: defi_chains for total value locked by chain, and defi_stablecoins for stablecoin supply and peg. It also makes the intended use clear through the resource scope and filters, leaving little ambiguity about when this tool is appropriate.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources