Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_options_summary

Retrieve historical options trading volume summaries for specific protocols to analyze decentralized exchange activity and market trends.

Instructions

GET /api/summary/options/{protocol}

Get summary of options dex volume with historical data.

Parameters:
    protocol: protocol slug (e.g., 'lyra')
    data_type: desired data type (default: 'dailyNotionalVolume')

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
protocolYes
data_typeNodailyNotionalVolume

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'get_options_summary' tool. It makes an API request to DefiLlama's /api/summary/options/{protocol} endpoint with the specified data_type parameter, returning the JSON response as a string. The @mcp.tool() decorator registers this function as a tool.
    @mcp.tool()
    async def get_options_summary(
        protocol: str,
        data_type: Literal['dailyPremiumVolume', 'dailyNotionalVolume'] = 'dailyNotionalVolume'
    ) -> str:
        """GET /api/summary/options/{protocol}
        
        Get summary of options dex volume with historical data.
        
        Parameters:
            protocol: protocol slug (e.g., 'lyra')
            data_type: desired data type (default: 'dailyNotionalVolume')
        """
        params = {'dataType': data_type}
        result = await make_request('GET', f'/api/summary/options/{protocol}', params)
        return str(result)
  • The @mcp.tool() decorator registers the get_options_summary function as an MCP tool.
    @mcp.tool()
  • Input schema defined by function parameters: protocol (str, required), data_type (Literal['dailyPremiumVolume', 'dailyNotionalVolume'], default='dailyNotionalVolume'). The docstring provides further description.
    protocol: str,
    data_type: Literal['dailyPremiumVolume', 'dailyNotionalVolume'] = 'dailyNotionalVolume'
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 states it's a GET operation, implying read-only behavior, but doesn't clarify aspects like rate limits, authentication needs, error handling, or what the historical data entails (e.g., time range, format). For a tool with no annotations, this leaves significant gaps in understanding its operational traits.

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 a clear purpose statement and parameter details. It avoids unnecessary fluff and is structured for quick comprehension, though it could be slightly more concise by integrating the parameter explanations more seamlessly.

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 has an output schema, the description doesn't need to explain return values, which is adequate. However, with no annotations, 2 parameters (one with low schema coverage), and complexity around options data, the description is minimal. It covers the basics but lacks depth on usage context, behavioral details, and parameter nuances, making it just sufficient but with clear gaps.

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

Parameters3/5

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

The description adds some meaning beyond the input schema by explaining that 'protocol' is a 'protocol slug' with an example ('lyra') and 'data_type' has a default value and specifies the data type. However, with 0% schema description coverage, it doesn't fully compensate for the lack of schema descriptions, as it doesn't detail the enum values' implications or provide further context for the 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: 'Get summary of options dex volume with historical data.' It specifies the action ('Get summary'), resource ('options dex volume'), and scope ('with historical data'), which is specific and informative. However, it doesn't explicitly distinguish this tool from sibling tools like 'get_options_overview' or 'get_options_overview_by_chain', which might also relate to options data.

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 the parameters but doesn't explain the context for selecting this tool over other options-related tools in the sibling list, such as 'get_options_overview' or 'get_options_overview_by_chain'. There are no usage prerequisites, exclusions, or comparisons provided.

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