Skip to main content
Glama
kukapay

dex-metrics-mcp

get_latest_trading_volume_by_aggregator

Retrieve 24-hour and 7-day trading volume data segmented by aggregator for DEX metrics analysis and reporting.

Instructions

Retrieve the latest 24-hour and 7-day trading volume by aggregator.

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

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Implementation Reference

  • main.py:65-83 (handler)
    Handler function for the 'get_latest_trading_volume_by_aggregator' tool. Decorated with @mcp.tool() for registration. Fetches latest trading volume data by aggregator from Dune query ID 21689, processes with pandas, and returns a markdown table.
    @mcp.tool()
    def get_latest_trading_volume_by_aggregator(limit: int = 1000) -> str:
        """
        Retrieve the latest 24-hour and 7-day trading volume by aggregator.
    
        Args:
            limit (int, optional): Maximum number of rows to retrieve from the query. Defaults to 1000.
    
        Returns:
            str: A markdown-formatted table of trading volume data, or an error message if the query fails.
        """
        try:
            data = get_latest_result(21689, limit=limit)
            df = pd.DataFrame(data)
            df = df.set_index("Rank")
            df = df.sort_index(ascending=True)
            return df.to_markdown()
        except Exception as e:
            return str(e)  
  • main.py:21-43 (helper)
    Helper function used by the tool to fetch the latest execution 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
Behavior2/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 mentions the return format ('markdown-formatted table') and error handling, but fails to address critical aspects such as data freshness, rate limits, authentication needs, or whether the operation is read-only or has side effects. This leaves significant gaps for a tool that likely queries live data.

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 front-loaded with the core purpose, followed by clear sections for arguments and returns. Every sentence adds value without redundancy, making it efficient and easy to parse.

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 lack of annotations and output schema, the description provides basic operational details (purpose, parameter, return format) but is incomplete. It misses behavioral traits like data latency or error conditions, and while it covers the parameter adequately, the overall context for a data retrieval tool in a sibling-rich environment is insufficient.

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 for the single parameter 'limit' by explaining its purpose ('Maximum number of rows to retrieve') and default value, which compensates for the 0% schema description coverage. However, it doesn't specify constraints like minimum/maximum values or how rows are ordered, leaving minor gaps.

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 verb ('Retrieve') and resource ('latest 24-hour and 7-day trading volume by aggregator'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_yoy_monthly_trading_volume_by_aggragator' or 'get_latest_trading_volume_by_dex', which would require more precise scope clarification.

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 like 'get_latest_trading_volume_by_dex' or other volume-related tools. The description lacks context about use cases, prerequisites, or exclusions, leaving the agent without direction for 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/kukapay/dex-metrics-mcp'

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