Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_options_overview_by_chain

Retrieve options DEX summaries with volume and historical data for a specific blockchain. Filter by data type and customize chart outputs.

Instructions

GET /api/overview/options/{chain}

List all options dexs along with summaries of their volumes and dataType history data filtering by chain.

Parameters:
    chain: chain name (e.g., 'ethereum')
    exclude_total_data_chart: true to exclude aggregated chart from response
    exclude_total_data_chart_breakdown: true to exclude broken down chart from response
    data_type: desired data type (default: 'dailyNotionalVolume')

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainYes
exclude_total_data_chartNo
exclude_total_data_chart_breakdownNo
data_typeNodailyNotionalVolume

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the get_options_overview_by_chain tool, registered via @mcp.tool() decorator. It constructs parameters and makes an API request to DefiLlama's /api/overview/options/{chain} endpoint to retrieve options DEX summaries filtered by chain.
    @mcp.tool()
    async def get_options_overview_by_chain(
        chain: str,
        exclude_total_data_chart: bool = True,
        exclude_total_data_chart_breakdown: bool = True,
        data_type: Literal['dailyPremiumVolume', 'dailyNotionalVolume'] = 'dailyNotionalVolume'
    ) -> str:
        """GET /api/overview/options/{chain}
        
        List all options dexs along with summaries of their volumes and dataType history data filtering by chain.
        
        Parameters:
            chain: chain name (e.g., 'ethereum')
            exclude_total_data_chart: true to exclude aggregated chart from response
            exclude_total_data_chart_breakdown: true to exclude broken down chart from response
            data_type: desired data type (default: 'dailyNotionalVolume')
        """
        params = {
            'excludeTotalDataChart': str(exclude_total_data_chart).lower(),
            'excludeTotalDataChartBreakdown': str(exclude_total_data_chart_breakdown).lower(),
            'dataType': data_type
        }
        result = await make_request('GET', f'/api/overview/options/{chain}', 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 describes a read operation ('List') but doesn't cover critical aspects like rate limits, authentication needs, error handling, or response format. While it hints at data filtering and exclusions, it lacks details on pagination, data freshness, or any side effects, leaving significant gaps for an AI agent.

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 and front-loaded, starting with the core purpose followed by parameter details. It uses bullet points for parameters, enhancing readability. However, the first sentence is slightly wordy ('summaries of their volumes and dataType history data'), and there's minor redundancy in parameter explanations, but overall it's efficient with zero wasted sentences.

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?

Given the tool's complexity (4 parameters, 1 required), no annotations, and the presence of an output schema, the description does a good job. It covers the purpose and parameters thoroughly, and since an output schema exists, it doesn't need to explain return values. However, it lacks behavioral context like rate limits or error handling, which slightly reduces completeness for a tool with no annotations.

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 each parameter: 'chain' is described with an example ('ethereum'), 'exclude_total_data_chart' and 'exclude_total_data_chart_breakdown' clarify what they exclude from the response, and 'data_type' specifies the default value and context. This compensates fully for the schema's lack of descriptions.

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: 'List all options dexs along with summaries of their volumes and dataType history data filtering by chain.' It specifies the verb ('List'), resource ('options dexs'), and scope ('filtering by chain'), making the action clear. However, it doesn't explicitly differentiate from sibling tools like 'get_options_overview' or 'get_options_summary', 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?

The description provides no guidance on when to use this tool versus alternatives. It mentions filtering by chain but doesn't compare to sibling tools such as 'get_options_overview' (which might not filter by chain) or 'get_options_summary' (which might provide different data). There's no mention of prerequisites, exclusions, or specific contexts for usage.

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