Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_dex_overview

Retrieve summaries of decentralized exchange volumes and historical data to analyze DEX performance and market trends.

Instructions

GET /api/overview/dexs

List all 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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
exclude_total_data_chartNo
exclude_total_data_chart_breakdownNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'get_dex_overview' tool, decorated with @mcp.tool(). It makes a GET request to the DefiLlama API endpoint '/api/overview/dexs' with optional parameters to exclude chart data and returns the JSON response as a string. The docstring provides the input schema description.
    async def get_dex_overview(
        exclude_total_data_chart: bool = True,
        exclude_total_data_chart_breakdown: bool = True
    ) -> str:
        """GET /api/overview/dexs
        
        List all 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
        """
        params = {
            'excludeTotalDataChart': str(exclude_total_data_chart).lower(),
            'excludeTotalDataChartBreakdown': str(exclude_total_data_chart_breakdown).lower()
        }
        result = await make_request('GET', '/api/overview/dexs', 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 behavior, but doesn't clarify aspects like authentication requirements, rate limits, response format, or pagination. For a tool with no annotations, this is a significant gap in transparency.

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 purpose, followed by parameter details. Every sentence adds value, with no redundant information. It could be slightly more structured with bullet points for parameters, but it remains efficient and clear.

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 an output schema exists, the description doesn't need to explain return values. However, with no annotations and 0% schema description coverage, it partially compensates with parameter semantics but lacks behavioral details like authentication or rate limits. For a tool with two parameters and sibling alternatives, this is adequate but leaves gaps in usage context.

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?

Schema description coverage is 0%, so the description must compensate. It provides clear semantics for 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 meaningful context beyond the schema's titles and types, though it doesn't cover default values or other nuances.

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 dexs along with summaries of their volumes and dataType history data.' It specifies the verb ('List'), resource ('dexs'), and what information is included ('summaries of their volumes and dataType history data'). However, it doesn't explicitly differentiate from sibling tools like 'get_dex_overview_by_chain' or 'get_dex_summary,' which would require a 5.

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_by_chain' or 'get_dex_summary,' nor does it specify any prerequisites or contexts for usage. This leaves the agent without clear 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