Skip to main content
Glama
kukapay

dex-metrics-mcp

get_weekly_trading_volume_by_dex

Retrieve weekly trading volume data for decentralized exchanges (DEXs) in a markdown-formatted pivot table with dates as index and DEX projects as columns.

Instructions

Retrieve weekly trading volume by decentralized exchange (DEX).

This tool fetches weekly trading volume data for various DEXs from a Dune Analytics query and returns it in a markdown-formatted pivot table, with dates as the index and DEX projects 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:129-150 (handler)
    The handler function decorated with @mcp.tool() implements the core logic: fetches data from Dune query 4323, processes it into a pivot table by date and DEX project using pandas, and returns markdown. Includes input validation via type hints and docstring, error handling.
    @mcp.tool()
    def get_weekly_trading_volume_by_dex(limit: int = 1000) -> str:
        """
        Retrieve weekly trading volume by decentralized exchange (DEX).
    
        This tool fetches weekly trading volume data for various DEXs from a Dune Analytics query and returns it in a markdown-formatted pivot table, with dates as the index and DEX projects 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(4323, limit=limit)
            df = pd.DataFrame(data)
            df["date"] = pd.to_datetime(df["_col1"]).dt.date
            pivot_df = df.pivot(index="date", columns="project", 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)
    Supporting helper function used by the tool to fetch the latest execution results from a specified Dune Analytics query using the Dune API.
    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. It discloses key behaviors: data source (Dune Analytics query), output format (markdown-formatted pivot table), and error handling (returns error message on query failure). However, it lacks details on rate limits, authentication needs, or data freshness, which are important for a data-fetching tool.

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 appropriately sized and front-loaded: the first sentence states the purpose clearly, followed by details on data source, output format, and parameter/return info. Every sentence adds value with no redundancy, making it efficient and well-structured.

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 (data retrieval with one parameter) and no annotations or output schema, the description is mostly complete: it covers purpose, data source, output format, parameter semantics, and error handling. However, it could improve by mentioning potential limitations like query performance or data latency, which are relevant for weekly volume data.

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 adds meaning by explaining the 'limit' parameter as 'Maximum number of rows to retrieve from the query' with a default of 1000, which clarifies its purpose beyond the schema's basic type and title. Since there is only one optional parameter, this is sufficient for a high score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Retrieve weekly trading volume by decentralized exchange'), identifies the resource (DEX trading volume data from Dune Analytics), and distinguishes it from siblings by specifying the weekly timeframe and DEX focus, unlike daily/monthly/YoY or chain/frontend/aggregator variants.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by specifying 'weekly trading volume by DEX,' which helps differentiate from siblings with different timeframes (e.g., daily, monthly) or scopes (e.g., by chain, frontend). However, it does not explicitly state when to use this tool versus alternatives or mention any exclusions, such as handling errors or prerequisites.

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