Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_price_chart

Retrieve historical price data for crypto tokens at specified intervals to analyze market trends and performance over time.

Instructions

GET /coins/chart/{coins}

Get token prices at regular time intervals.

Parameters:
    coins: comma-separated tokens in format {chain}:{address}
    start: unix timestamp of earliest data point
    end: unix timestamp of latest data point
    span: number of data points returned
    period: duration between data points (default: '24h')
    search_width: time range on either side to find price data (default: '600')

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinsYes
startNo
endNo
spanNo
periodNo24h
search_widthNo600

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'get_price_chart' tool, registered via @mcp.tool(). It constructs parameters and calls the DefiLlama API endpoint /coins/chart/{coins} to retrieve token price charts at regular intervals.
    @mcp.tool()
    async def get_price_chart(
        coins: str,
        start: Optional[int] = None,
        end: Optional[int] = None,
        span: Optional[int] = None,
        period: str = "24h",
        search_width: str = "600"
    ) -> str:
        """GET /coins/chart/{coins}
        
        Get token prices at regular time intervals.
        
        Parameters:
            coins: comma-separated tokens in format {chain}:{address}
            start: unix timestamp of earliest data point
            end: unix timestamp of latest data point
            span: number of data points returned
            period: duration between data points (default: '24h')
            search_width: time range on either side to find price data (default: '600')
        """
        params = {
            'period': period,
            'searchWidth': search_width
        }
        if start is not None:
            params['start'] = start
        if end is not None:
            params['end'] = end
        if span is not None:
            params['span'] = span
        result = await make_request('GET', f'/coins/chart/{coins}', params)
        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 the full burden of behavioral disclosure. It mentions the tool fetches price data at intervals, but lacks critical details: it doesn't specify if this is a read-only operation (implied by 'GET' but not explicit), what the output format is (though an output schema exists), rate limits, authentication needs, or error handling. For a data-fetching tool with 6 parameters, this leaves significant gaps in understanding its behavior.

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 well-structured and appropriately sized. It starts with the purpose, lists parameters with clear explanations, and uses bullet-like formatting for readability. Every sentence adds value, with no redundant information. It could be slightly more concise by integrating the purpose into the parameter list, but overall it's efficient.

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 complexity (6 parameters, no annotations), the description does a decent job but has gaps. It fully documents parameters, which is crucial with 0% schema coverage, and an output schema exists to handle return values. However, it lacks behavioral context like rate limits or error scenarios, and doesn't differentiate from sibling tools, leaving the agent to guess when to use it. This is adequate but not comprehensive.

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

Parameters5/5

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

The description adds substantial meaning beyond the input schema, which has 0% description coverage. It explains all 6 parameters in detail: 'coins' as 'comma-separated tokens in format {chain}:{address}', 'start' and 'end' as Unix timestamps, 'span' as 'number of data points returned', and default values for 'period' and 'search_width'. This fully compensates for the schema's lack of descriptions, making parameter usage clear.

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: 'Get token prices at regular time intervals.' This specifies the verb ('Get') and resource ('token prices'), and the URL path '/coins/chart/{coins}' reinforces it's about price charts for tokens. However, it doesn't explicitly differentiate from sibling tools like 'get_current_prices' or 'get_historical_prices', which might offer similar data in different formats or scopes.

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. It doesn't mention sibling tools like 'get_current_prices' (for real-time prices) or 'get_historical_prices' (which might serve a similar purpose), nor does it specify prerequisites or exclusions (e.g., time range constraints). The agent must infer usage from the tool name and parameters alone.

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