Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_dex_summary

Retrieve DEX volume summaries with historical data for specific protocols like Uniswap. Access aggregated and broken-down chart data to analyze decentralized exchange performance.

Instructions

GET /api/summary/dexs/{protocol}

Get summary of dex volume with historical data.

Parameters:
    protocol: protocol slug (e.g., 'uniswap')
    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 main handler function for the 'get_dex_summary' MCP tool. It is decorated with @mcp.tool() for registration and implements the logic to query the DefiLlama API endpoint /api/summary/dexs/{protocol}, constructing parameters for chart exclusions, making an async HTTP request via the shared make_request helper, and returning the JSON response as a string.
    @mcp.tool()
    async def get_dex_summary(
        protocol: str,
        exclude_total_data_chart: bool = True,
        exclude_total_data_chart_breakdown: bool = True
    ) -> str:
        """GET /api/summary/dexs/{protocol}
        
        Get summary of dex volume with historical data.
        
        Parameters:
            protocol: protocol slug (e.g., 'uniswap')
            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/dexs/{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 states this is a GET operation (implying read-only) and mentions historical data, but doesn't cover critical aspects like authentication requirements, rate limits, error handling, pagination, or response format. For a tool with no annotation coverage, 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, with the core purpose stated first. The parameter explanations are clear and necessary. However, the inclusion of the HTTP method 'GET /api/summary/dexs/{protocol}' is redundant with the tool name and could be omitted for better conciseness.

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, 1 required), no annotations, and the presence of an output schema, the description is partially complete. It covers the purpose and parameters adequately but lacks behavioral details (e.g., auth, errors) and usage guidelines. The output schema likely handles return values, so that gap is mitigated, but overall completeness is limited.

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 context beyond the input schema. While the schema has 0% description coverage (only titles), the description explains that 'protocol' is a 'slug (e.g., 'uniswap')' and clarifies the boolean parameters control exclusion of specific chart types from the response. This compensates well for the schema's lack of descriptions, though it doesn't detail all possible protocol values or chart formats.

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 dex volume with historical data.' It specifies the verb ('Get'), resource ('summary of dex volume'), and scope ('with historical data'). However, it doesn't explicitly differentiate from sibling tools like 'get_dex_overview' or 'get_dex_overview_by_chain', which might provide overlapping functionality.

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_dex_overview' or 'get_dex_overview_by_chain', nor does it specify prerequisites, exclusions, or appropriate contexts for usage. The only implied usage is based on the parameter descriptions, but no explicit guidelines are given.

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