Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_derivatives_summary

Retrieve volume details for a specific perpetual protocol to analyze derivatives market data and performance metrics.

Instructions

GET /api/summary/derivatives/{protocol}

Volume Details about a specific perp protocol.

Parameters:
    protocol: protocol slug (e.g., 'hyperliquid')
    exclude_total_data_chart: true to exclude aggregated chart from response
    exclude_total_data_chart_breakdown: true to exclude broken down chart from response

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
protocolYes
exclude_total_data_chartNo
exclude_total_data_chart_breakdownNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'get_derivatives_summary' tool. It is decorated with @mcp.tool(), which registers it with the MCP server. The function makes an HTTP request to the DefiLlama API for derivatives summary data for a given protocol and returns the result as a string.
    @mcp.tool()
    async def get_derivatives_summary(
        protocol: str,
        exclude_total_data_chart: bool = False,
        exclude_total_data_chart_breakdown: bool = False
    ) -> str:
        """GET /api/summary/derivatives/{protocol}
        
        Volume Details about a specific perp protocol.
        
        Parameters:
            protocol: protocol slug (e.g., 'hyperliquid')
            exclude_total_data_chart: true to exclude aggregated chart from response
            exclude_total_data_chart_breakdown: true to exclude broken down chart from response
        """
        params = {
            'excludeTotalDataChart': str(exclude_total_data_chart).lower(),
            'excludeTotalDataChartBreakdown': str(exclude_total_data_chart_breakdown).lower()
        }
        result = await make_request('GET', f'/api/summary/derivatives/{protocol}', 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 is a GET operation and describes some response exclusions, but does not cover critical aspects like rate limits, authentication needs, error handling, or the structure of the returned volume details. For a tool with no annotations, 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 appropriately sized and front-loaded, starting with the purpose and followed by parameter details. It uses bullet points for parameters, making it easy to scan. However, the first sentence could be more polished, and some redundancy exists (e.g., repeating 'total data chart'), but overall it is efficient with minimal waste.

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 (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 and usage guidelines. The presence of an output schema means return values are documented elsewhere, so the description's focus on parameters is acceptable, but overall completeness is moderate due to missing operational details.

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 meaningful semantics beyond the input schema, which has 0% description coverage. It explains that 'protocol' is a 'slug (e.g., 'hyperliquid')' and clarifies the boolean parameters as exclusions for specific chart types. This compensates well for the schema's lack of descriptions, though it could provide more context on protocol options or chart details.

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: 'Volume Details about a specific perp protocol.' It specifies the verb ('GET') and resource ('derivatives summary'), but does not explicitly differentiate it from sibling tools like 'get_derivatives_overview' or 'get_options_summary', which might have overlapping scopes. The purpose is clear but lacks sibling distinction.

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 is provided on when to use this tool versus alternatives. The description does not mention any context, prerequisites, or exclusions, such as when to choose this over 'get_derivatives_overview' or other summary tools. Usage is implied only by the parameter details, with no explicit guidelines.

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