Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_options_overview

Retrieve summaries of options DEX volumes and historical data to analyze market activity and trends across platforms.

Instructions

GET /api/overview/options

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

Parameters:
    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
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' tool. It is registered via @mcp.tool() decorator and implements the logic to fetch options DEX overview data from the DefiLlama API by constructing parameters and calling make_request. The function signature and docstring define the input schema.
    async def get_options_overview(
        exclude_total_data_chart: bool = True,
        exclude_total_data_chart_breakdown: bool = True,
        data_type: Literal['dailyPremiumVolume', 'dailyNotionalVolume'] = 'dailyNotionalVolume'
    ) -> str:
        """GET /api/overview/options
        
        List all options dexs along with summaries of their volumes and dataType history data.
        
        Parameters:
            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', '/api/overview/options', params)
        return str(result)
  • The @mcp.tool() decorator registers the get_options_overview function as an MCP tool.
    async def get_options_overview(
  • The docstring provides the description and parameter details serving as the tool schema documentation.
    """GET /api/overview/options
    
    List all options dexs along with summaries of their volumes and dataType history data.
    
    Parameters:
        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')
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool is a GET endpoint for listing data, implying it's a read-only operation, but doesn't clarify permissions, rate limits, response format, or pagination. For a tool with zero annotation coverage, this is insufficient to ensure 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.

Conciseness4/5

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

The description is appropriately sized and front-loaded, starting with the HTTP method and endpoint, followed by the core purpose, then parameter details. Each sentence adds value without redundancy. It could be slightly more structured by separating the purpose from parameters with a line break, 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 moderate complexity (3 parameters, no annotations, but with an output schema), the description is partially complete. It covers the purpose and parameters adequately, but lacks behavioral context like error handling or response structure. The presence of an output schema mitigates some gaps, but without annotations, more guidance on usage and safety would improve completeness.

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 description adds significant value beyond the input schema, which has 0% description coverage. It explains all three parameters: 'exclude_total_data_chart' and 'exclude_total_data_chart_breakdown' control chart exclusions, and 'data_type' specifies the desired data type with its default. This compensates well for the schema's lack of descriptions, though it doesn't detail the enum values beyond the default.

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.' It specifies the verb ('List'), resource ('options dexs'), and scope ('summaries of their volumes and dataType history data'). However, it doesn't explicitly differentiate from sibling tools like 'get_options_overview_by_chain' 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 doesn't mention sibling tools like 'get_options_overview_by_chain' or 'get_options_summary', nor does it specify any prerequisites, exclusions, or contextual cues for usage. This leaves the agent without direction on tool selection.

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