Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_derivatives_overview

Retrieve summaries and volume data for all derivatives across blockchain networks, with options to filter chart data in the response.

Instructions

GET /api/overview/derivatives

Lists all derivatives along summaries of their volumes filtering by chain.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
exclude_total_data_chartNo
exclude_total_data_chart_breakdownNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'get_derivatives_overview' tool. It uses the @mcp.tool() decorator for registration and defines input parameters with defaults. It constructs API parameters and calls the shared make_request helper to fetch data from DefiLlama's /api/overview/derivatives endpoint, returning the JSON response as a string.
    @mcp.tool()
    async def get_derivatives_overview(
        exclude_total_data_chart: bool = False,
        exclude_total_data_chart_breakdown: bool = False
    ) -> str:
        """GET /api/overview/derivatives
        
        Lists all derivatives along summaries of their volumes filtering by chain.
        
        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
        """
        params = {
            'excludeTotalDataChart': str(exclude_total_data_chart).lower(),
            'excludeTotalDataChartBreakdown': str(exclude_total_data_chart_breakdown).lower()
        }
        result = await make_request('GET', '/api/overview/derivatives', params)
        return str(result)
  • Input schema defined by function parameters: exclude_total_data_chart (bool, default False), exclude_total_data_chart_breakdown (bool, default False). Output is str (API response). Docstring provides further description.
    async def get_derivatives_overview(
        exclude_total_data_chart: bool = False,
        exclude_total_data_chart_breakdown: bool = False
    ) -> str:
  • The @mcp.tool() decorator registers this function as an MCP tool named 'get_derivatives_overview' (inferred from function name).
    @mcp.tool()
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While it mentions the tool lists derivatives with volume summaries filtered by chain, it doesn't describe important behavioral aspects: whether this is a read-only operation, what permissions might be needed, how results are formatted, whether there are rate limits, or what the output contains beyond the chart exclusion parameters. The description provides minimal behavioral context.

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 concise with three sentences that each serve a purpose: stating the endpoint, explaining the tool's function, and detailing parameters. It's front-loaded with the core functionality. While efficient, the inclusion of the endpoint path 'GET /api/overview/derivatives' might be slightly redundant if the tool name already conveys this information.

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 that there's an output schema (which reduces the need to describe return values), 0 required parameters, and only 2 boolean parameters, the description is reasonably complete for this level of complexity. However, as a data retrieval tool with no annotations, it should ideally mention that this is a read-only operation and provide more context about the filtering mechanism ('by chain'). The parameter explanations are strong, but overall behavioral context is lacking.

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 provides excellent parameter semantics despite 0% schema description coverage. It clearly explains both parameters: 'exclude_total_data_chart: true to exclude aggregated chart from response' and 'exclude_total_data_chart_breakdown: true to exclude broken down chart from response.' This adds crucial meaning beyond the schema's bare boolean types and titles, explaining what these parameters actually control in the response.

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: 'Lists all derivatives along summaries of their volumes filtering by chain.' This specifies the verb (lists), resource (derivatives), and scope (summaries of volumes filtered by chain). However, it doesn't explicitly differentiate from sibling tools like 'get_derivatives_summary' or 'get_options_overview', which appear to be related derivatives/options tools.

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. With sibling tools like 'get_derivatives_summary' and 'get_options_overview' available, there's no indication of how this tool differs or when it should be preferred. The mention of 'filtering by chain' might imply some context, but no explicit usage instructions are 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