Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_yield_pools_borrow

Retrieve borrow cost APY data from lending markets to analyze borrowing rates across DeFi protocols.

Instructions

GET /yields/poolsBorrow

Borrow costs APY of assets from lending markets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'get_yield_pools_borrow' tool. It is registered using the @mcp.tool() decorator, which also serves as the registration. The function makes an API request to the DefiLlama '/yields/poolsBorrow' endpoint using the shared make_request helper and returns the JSON response as a string. No input parameters are required.
    @mcp.tool()
    async def get_yield_pools_borrow() -> str:
        """GET /yields/poolsBorrow
        
        Borrow costs APY of assets from lending markets.
        """
        result = await make_request('GET', '/yields/poolsBorrow')
        return str(result)
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral insight. It mentions the action (GET) and data type (borrow costs APY), but fails to disclose critical traits like rate limits, authentication needs, error handling, or response format, which are essential for safe and effective use.

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 concise with three lines, but it includes redundant information (the endpoint 'GET /yields/poolsBorrow') that may not add value beyond the tool name. The core purpose is stated clearly, but the structure could be more streamlined by focusing solely on the functional description.

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 the tool's simplicity (0 parameters, output schema exists), the description is minimally adequate. However, it lacks details on behavioral aspects like data freshness, scope (e.g., all assets or filtered), or integration context, which would enhance completeness for effective agent use.

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 tool has 0 parameters with 100% schema description coverage, so no parameter information is needed. The description doesn't add param details, but this is acceptable given the lack of parameters, aligning with the baseline for zero parameters.

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

Purpose4/5

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

The description clearly states the tool's purpose: retrieving borrow costs APY of assets from lending markets. It specifies the resource (borrow costs APY) and action (GET), though it doesn't explicitly differentiate from sibling tools like 'get_yield_pools' or 'get_yield_pools_old', which prevents a perfect score.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about use cases, prerequisites, or comparisons to sibling tools such as 'get_yield_pools' or 'get_yield_chart_lend_borrow', leaving the agent without 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