Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_fdv_performance

Retrieve performance charts for crypto narratives by category, weighted by market capitalization, across specified time periods.

Instructions

GET /fdv/performance/{period}

Get chart of narratives based on category performance (with individual coins weighted by mcap).

Parameters:
    period: One of ['7', '30', 'ytd', '365']

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
periodYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function implementing the get_fdv_performance tool. Registered via @mcp.tool() decorator. Validates period input, fetches data from DefiLlama API /fdv/performance/{period}, and returns JSON string. Type hints provide input schema (period as Literal).
    @mcp.tool()
    async def get_fdv_performance(period: Literal['7', '30', 'ytd', '365']) -> str:
        """GET /fdv/performance/{period}
        
        Get chart of narratives based on category performance (with individual coins weighted by mcap).
        
        Parameters:
            period: One of ['7', '30', 'ytd', '365']
        """
        if period not in ['7', '30', 'ytd', '365']:
            raise ValueError("Period must be one of: '7', '30', 'ytd', '365'")
        result = await make_request('GET', f'/fdv/performance/{period}')
        return str(result)
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 describes a read operation ('Get chart') but doesn't disclose behavioral traits like authentication needs, rate limits, error handling, or what 'chart' entails (e.g., format, size). The mention of 'narratives' and 'weighted by mcap' adds some context, but key operational details are missing.

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

Conciseness4/5

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

The description is appropriately sized with three sentences: purpose, parameter explanation, and a brief note on weighting. It's front-loaded with the main action. No wasted words, though it could be slightly more structured (e.g., bullet points for parameters).

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 one parameter with good description coverage and an output schema (implied by context signals), the description is adequate for basic use. However, without annotations and with vague terms like 'narratives' and 'chart', it lacks completeness for understanding the tool's full behavior and output. Sibling tools suggest this is part of a financial data API, but the description doesn't integrate that context.

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 description coverage is 0%, but the description compensates by explaining the 'period' parameter with its enum values ['7', '30', 'ytd', '365']. This adds meaning beyond the schema's title 'Period', clarifying the specific time intervals. Since there's only one parameter, this is sufficient for good understanding.

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

Purpose3/5

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

The description states 'Get chart of narratives based on category performance' which provides a general purpose, but it's vague about what 'narratives' and 'category performance' specifically mean. It mentions coins weighted by market cap, but doesn't clarify the resource or output format. Compared to siblings like 'get_categories' or 'get_price_chart', the distinction is unclear.

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 on when to use this tool versus alternatives is provided. The description doesn't mention any prerequisites, exclusions, or suggest other tools for related tasks. Given many sibling tools for data retrieval (e.g., 'get_categories', 'get_price_chart'), the lack of comparative context leaves usage ambiguous.

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