Skip to main content
Glama
kukapay

dex-metrics-mcp

get_yoy_monthly_trading_volume_by_aggragator

Analyze year-over-year monthly trading volume trends for aggregators using Dune Analytics data, presented in a markdown pivot table format.

Instructions

Retrieve year-over-year monthly trading volume by aggregator.

This tool fetches year-over-year monthly trading volume data for aggregators from a Dune Analytics query and returns it in a markdown-formatted pivot table, with years as the index and months as columns.

Args:
    limit (int, optional): Maximum number of rows to retrieve from the query. Defaults to 1000.

Returns:
    str: A markdown-formatted pivot table of trading volume data, or an error message if the query fails.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Implementation Reference

  • main.py:175-195 (handler)
    The main handler function for the tool 'get_yoy_monthly_trading_volume_by_aggragator'. It is decorated with @mcp.tool() which serves as both the implementation and registration. Fetches data from Dune query 4424 using the helper get_latest_result, pivots the data by year and month, and returns a markdown table.
    @mcp.tool()
    def get_yoy_monthly_trading_volume_by_aggragator(limit: int = 1000) -> str:
        """
        Retrieve year-over-year monthly trading volume by aggregator.
    
        This tool fetches year-over-year monthly trading volume data for aggregators from a Dune Analytics query and returns it in a markdown-formatted pivot table, with years as the index and months as columns.
    
        Args:
            limit (int, optional): Maximum number of rows to retrieve from the query. Defaults to 1000.
    
        Returns:
            str: A markdown-formatted pivot table of trading volume data, or an error message if the query fails.
        """
        try:
            data = get_latest_result(4424, limit=limit)
            df = pd.DataFrame(data)
            pivot_df = df.pivot(index="year", columns="month", values="usd_volume")
            pivot_df = pivot_df.sort_index(ascending=False)
            return pivot_df.to_markdown()
        except Exception as e:
            return str(e)  
  • main.py:21-43 (helper)
    Shared helper function used by multiple tools, including this one, to fetch latest results from a specified Dune Analytics query ID.
    def get_latest_result(query_id: int, limit: int = 1000) -> list:
        """
        Fetch the latest results from a Dune Analytics query.
    
        Args:
            query_id (int): The ID of the Dune query to fetch results from.
            limit (int, optional): Maximum number of rows to return. Defaults to 1000.
    
        Returns:
            list: A list of dictionaries containing the query results, or an empty list if the request fails.
    
        Raises:
            httpx.HTTPStatusError: If the API request fails due to a client or server error.
        """
        url = f"{BASE_URL}/query/{query_id}/results"
        params = {"limit": limit}
        with httpx.Client() as client:
            response = client.get(url, params=params, headers=HEADERS, timeout=300)
            response.raise_for_status()
            data = response.json()
            
        result_data = data.get("result", {}).get("rows", [])
        return result_data
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds useful context: data comes from 'Dune Analytics query,' returns 'markdown-formatted pivot table,' and may return 'an error message if the query fails.' However, it lacks details on permissions, rate limits, query execution time, or what constitutes a 'failure.' For a data-fetching tool with zero annotation coverage, this is adequate but leaves gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and concise. It opens with a clear purpose statement, elaborates on data source and format, and includes dedicated Args and Returns sections. Every sentence adds value without redundancy, and it's appropriately sized for the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 (1 parameter, no annotations, no output schema), the description is reasonably complete. It covers purpose, data source, output format, parameter meaning, and error handling. However, without annotations or output schema, it could benefit from more behavioral details (e.g., query constraints, authentication needs) to be fully comprehensive.

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. The schema only documents 'limit' as an integer with default 1000 (0% coverage). The description clarifies it's the 'Maximum number of rows to retrieve from the query,' explaining its purpose. Since there's only one parameter and the description compensates well for the low schema coverage, this earns a high score.

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: 'Retrieve year-over-year monthly trading volume by aggregator' and 'fetches year-over-year monthly trading volume data for aggregators from a Dune Analytics query.' It specifies the verb (retrieve/fetch), resource (trading volume data), and scope (year-over-year monthly, by aggregator). However, it doesn't explicitly differentiate from sibling tools like 'get_latest_trading_volume_by_aggregator' or 'get_monthly_trading_volume_by_dex' beyond the 'year-over-year monthly' aspect.

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 or explain scenarios where this specific year-over-year monthly aggregator data is needed compared to daily, weekly, latest, or dex-focused volume tools. Usage context is implied but not explicit.

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/kukapay/dex-metrics-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server