Skip to main content
Glama

yield-farming-active

Return active DeFi yield farming pools sorted by 30-day average APY from DeFiLlama. Filter by chain, protocol, TVL, APY, or stablecoin-only for yield research.

Instructions

Returns active DeFi yield farming pools sorted by 30-day average APY. Sourced from DeFiLlama (free, no key). Each pool includes protocol, chain, symbol, TVL, current APY, 30-day mean APY, impermanent-loss risk, and stablecoin flag. Filter by chain, protocol, minimum TVL, minimum APY, or stablecoin-only pools. Use for portfolio yield research, pre-trade DeFi reconnaissance, or capital allocation decisions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoFilter by blockchain (e.g. 'Ethereum', 'Base', 'Polygon', 'Arbitrum', 'Solana'). Case-insensitive. Omit for all chains.
protocolNoFilter by protocol name (e.g. 'aave-v3', 'uniswap-v3', 'curve', 'lido'). Case-insensitive substring match.
min_tvl_usdNoMinimum Total Value Locked in USD. Default 1000000 ($1M). Lower values include smaller pools with potentially higher (but riskier) yields.
min_apyNoMinimum APY percentage to include (based on 30-day mean). Default 0. E.g. 5 returns pools yielding ≥5% annualized.
stablecoin_onlyNoIf true, returns only stablecoin pools (no impermanent loss from token price volatility). Default false.
sort_byNoSort order: 'apy_30d' (30-day average APY, default and most stable), 'apy_current' (live APY, more volatile), 'tvl' (largest pools first).
limitNoNumber of pools to return (1–50, default 20).
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the data source (DeFiLlama, free, no key) and lists included fields. However, it does not mention update frequency, rate limits, or error behavior, which are important for an agent.

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?

Two sentences front-load the core purpose and then detail contents and filters. Every sentence adds value with no redundancy.

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

Completeness4/5

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

For a simple list tool with no output schema, the description covers purpose, source, fields, filters, and use cases. It could mention data freshness or caching behavior, but overall it is complete for its complexity.

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 coverage is 100%, so baseline is 3. The description adds a summary of filter options but does not add meaning beyond the schema's detailed parameter descriptions. It provides context but no new depth.

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 returns active DeFi yield farming pools sorted by 30-day average APY, with specific verb, resource, and key attributes. It distinguishes from sibling tools by focusing on active pools and APY sorting.

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?

The description provides explicit use cases: portfolio yield research, pre-trade DeFi reconnaissance, capital allocation decisions. It does not explicitly exclude alternative tools but gives clear context for when to use this tool.

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/thebrierfox/the-stall'

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