Skip to main content
Glama
ymylive
by ymylive

list_yield_pools

List DeFi yield-bearing pools (lending, staking, LPs) filtered and ranked by APY or TVL. Supports filters for min TVL, project, chain, symbol, and sorting by APY, TVL, or mean APY.

Instructions

List DeFi yield-bearing pools (lending, staking, LPs) filtered & ranked by APY or TVL.

The DefiLlama yields endpoint returns ~20k pools, so this tool aggressively filters and slices client-side. Use for "best stablecoin yields right now", "highest APY on Aave", "Lido vs Rocket Pool TVL", etc. Pair with list_protocols if you want protocol-level TVL rather than per-pool APY.

Args: min_tvl_usd: Minimum pool TVL in USD. Default 1M filters out tiny pools. Set to 0 to disable. project: Optional project filter, e.g. "aave-v3", "lido", "compound-v3". Matches the project field, case-insensitive. chain: Optional chain filter, e.g. "Ethereum", "Solana", "Arbitrum". Case-insensitive exact match against chain. symbol: Optional symbol/token substring filter, e.g. "USDC", "ETH", "STETH". Case-insensitive substring match against symbol. limit: Number of pools to return after filtering & sorting (1..500). sort_by: Metric to rank by, descending. "apy" = current APY, "tvlUsd" = pool size, "apyMean30d" = 30-day mean APY.

Returns: Array of pool summaries with pool (DefiLlama pool id), chain, project, symbol, tvlUsd, apy, apyBase, apyReward, apyMean30d, apyPct1D, apyPct7D, apyPct30D, stablecoin, ilRisk, exposure, predictions, rewardTokens, underlyingTokens.

Note: project/chain/symbol (when non-empty) are validated. project and chain use ^[a-z0-9][a-z0-9._-]{0,127}$; symbol allows mixed case via ^[A-Za-z0-9._-]{0,63}$.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
min_tvl_usdNo
projectNo
chainNo
symbolNo
limitNo
sort_byNoapy
Behavior4/5

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

The description explains client-side aggressive filtering, pool count (~20k), validation of parameters, and default behaviors. It does not explicitly state read-only nature but implies it. Without annotations, this provides substantial transparency.

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?

Well-structured with clear sections: purpose, usage, args, returns, note. Every sentence adds value, and core purpose is front-loaded. No redundancy.

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 no output schema, it lists all return fields comprehensively. All 6 parameters are explained, validation details provided, and edge cases addressed (default 1M, disable by 0). The tool's behavior is fully specified.

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?

Despite 0% schema coverage, the description explains every parameter in detail: defaults, filtering behavior, case-insensitivity, value ranges (limit 1-500), and enum meanings. Regex patterns add extra clarity.

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 defines the tool as listing DeFi yield-bearing pools with filtering and ranking by APY/TVL. It uses specific verbs and resource, and distinguishes from sibling 'list_protocols' by noting different use cases.

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?

Explicit usage scenarios are given (e.g., 'best stablecoin yields', 'highest APY on Aave'), and an alternative tool is mentioned for protocol-level TVL, guiding when to use this vs. siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ymylive/coin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server