AlphaGrowth

DeFi yield pools

yield_pools

Read-only

DeFi yield and lending pools across protocols and chains, updated hourly: supply APY (base + reward), borrow APY for lending pools, TVL and what it counts, 50 per page. Filter by chain, token symbol, stablecoins only and a minimum TVL (use min_tvl_usd of 1000000 or more to skip thin pools, whose APYs swing). Each pool links to its page with the daily history; yield_pool returns that history. Free data from AlphaGrowth (alphagrowth.io).

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": "yield_pools"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Page number, 50 pools per page.
`chain`	No	The chain's AlphaGrowth slug (as in /apr/chains/<slug>, e.g. base, ethereum, solana).
`token`	No	A token symbol, matched exactly, case-insensitive (e.g. WETH, WBTC).
`sort_by`	No	tvl, supply_apy or borrow_apy.	tvl
`sort_order`	No	desc for the highest first, asc for the lowest.	desc
`min_tvl_usd`	No	The smallest TVL in USD a pool needs to be listed.
`stablecoins_only`	No	yes for stablecoin pools only.	no

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only cover safety (readOnlyHint, openWorldHint), so the description carries the rest and does: hourly refresh cadence, page size of 50, TVL semantics, and a data-quality caveat that thin pools have volatile APYs. It also credits the upstream data source (AlphaGrowth), which matters for trust and licensing.

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-loaded with what the resource is and what it returns, then filtering guidance, then sibling routing. Every clause carries information; nothing is restated from the name or title.

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 seven optional parameters, no required ones, and no output schema, the description supplies what is otherwise missing: the shape of returned fields, pagination behavior, data freshness, provenance, and when to escalate to yield_pool for history. An agent has everything needed to call this correctly on the first try.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning by recommending a concrete min_tvl_usd threshold and explaining why (thin pools distort APYs). It also confirms the filter dimensions map to chain, token and stablecoin-only, though it adds no syntax detail for chain slugs or token matching beyond what the schema already states.

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?

States a specific resource (DeFi yield and lending pools across protocols and chains) and what it returns: supply APY base+reward, borrow APY for lending pools, TVL, paginated 50 at a time. It also distinguishes itself from the sibling yield_pool, which returns per-pool history, so an agent can pick without opening either schema.

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?

Names the available filters (chain, token symbol, stablecoins only, min TVL) and gives concrete selection advice: use min_tvl_usd of 1000000 or more to skip thin pools whose APYs swing. It explicitly routes detail lookups to yield_pool, so the this-vs-sibling decision is fully specified.

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

All AlphaGrowth 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.

Resources

Need Help?