Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_yield_pools_old

Retrieve historical yield pool data from DeFiLlama Pro, including pool addresses, for crypto investment analysis and research.

Instructions

GET /yields/poolsOld

Same as /pools but it also includes a new parameter `pool_old` which usually contains pool address.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'get_yield_pools_old' tool. It is decorated with @mcp.tool(), which also serves as the registration mechanism in FastMCP. The function makes an API request to the DefiLlama /yields/poolsOld endpoint and returns the result as a string.
    @mcp.tool()
    async def get_yield_pools_old() -> str:
        """GET /yields/poolsOld
        
        Same as /pools but it also includes a new parameter `pool_old` which usually contains pool address.
        """
        result = await make_request('GET', '/yields/poolsOld')
        return str(result)
  • Shared helper function used by get_yield_pools_old (and other tools) to perform HTTP requests to the DefiLlama API.
    async def make_request(method: str, endpoint: str, params: Optional[Dict[str, Any]] = None) -> Any:
        """Make a request to the DefiLlama API."""
        try:
            response = await client.request(method, endpoint, params=params)
            response.raise_for_status()
            return response.json()
        except Exception as e:
            return f"Error: {str(e)}"
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions a parameter 'pool_old' but doesn't disclose behavioral traits like whether this is a read-only operation, what data format is returned, or any constraints. The description is insufficient for understanding how the tool behaves beyond a vague parameter mention.

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

Conciseness3/5

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

The description is brief but poorly structured. It starts with 'GET /yields/poolsOld' which is redundant with the tool name, and the second sentence adds minimal context. While concise, it lacks front-loaded clarity and wastes space on tautological elements.

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

Completeness3/5

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

Given 0 parameters and an output schema exists, the description doesn't need to explain return values. However, with no annotations and a vague purpose, it fails to provide complete context for tool selection. It's minimally adequate but has clear gaps in explaining what this tool does compared to siblings.

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?

The input schema has 0 parameters with 100% coverage, so no parameters need documentation. The description mentions a parameter 'pool_old' which might be confusing since the schema shows none, but this doesn't negatively impact the score as the baseline for 0 parameters is 4. No additional parameter semantics are needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Same as /pools' which is tautological with the tool name 'get_yield_pools_old' and doesn't clearly articulate what the tool does. It mentions a parameter 'pool_old' but doesn't explain what resource or data this tool retrieves. The purpose remains vague and circular.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'get_yield_pools' or 'get_yield_pools_borrow' from the sibling list. It only mentions a parameter difference without context on use cases or exclusions, leaving the agent with no usage direction.

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/0xReisearch/crypto-mcp-beta'

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