AlphaGrowth

DeFi yield pool

yield_pool

Read-only

One DeFi yield pool by id (as listed by yield_pools): latest supply and borrow APYs, TVL, its daily APY and TVL history over the last days days, and up to five larger pools of the same token on other protocols or chains. Free data from AlphaGrowth (alphagrowth.io).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	The pool id (a UUID), as yield_pools lists it.
`days`	No	How many days of daily history, the latest last.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful context beyond them: the data is free from AlphaGrowth, history is bounded by `days`, and results include up to five larger pools of the same token. It omits error behavior when an id is unknown or whether responses are cached.

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?

A single dense sentence that front-loads the identity of the tool and then enumerates the payload. Every clause (APYs, TVL, history, comparable pools, data source) carries information; nothing repeats the name or schema.

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?

With no output schema, the description bears the burden of describing return values, and it does so thoroughly, plus it caps the comparables at five. It falls just short of complete by not covering the not-found case or the shape/units of the history series.

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 baseline is 3, but the description adds meaning: `days` controls the daily APY/TVL history window, with the latest entry last. `id` is tied explicitly to yield_pools' listing, which helps an agent source a valid UUID.

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 verb and resource: fetch one DeFi yield pool by id, and enumerates exactly what comes back (supply/borrow APYs, TVL, daily history, comparable pools). It also names yield_pools as the source of ids, so an agent can distinguish it from the sibling list tool 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 Guidelines4/5

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

The phrase 'as listed by yield_pools' establishes the intended call sequence (list, then fetch by id). It does not state exclusions, e.g. that this should not be used to scan many pools or how to choose `days`, so it is clear context without explicit alternatives.

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?