Skip to main content
Glama

get_average_price_by_collection

Calculate average selling prices for NFT collections to analyze market trends and value insights using Dune Analytics data.

Instructions

Retrieve average selling price for NFT collections.

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

Returns:
    str: Markdown table of average prices by collection, or error message if the query fails.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Implementation Reference

  • main.py:88-103 (handler)
    The handler function for the 'get_average_price_by_collection' tool. It fetches the latest results from Dune query ID 5140470, converts to a Pandas DataFrame, and returns a Markdown table of average prices by collection.
    def get_average_price_by_collection(limit: int = 1000) -> str:
        """
        Retrieve average selling price for NFT collections.
    
        Args:
            limit (int, optional): Maximum number of rows to fetch from the query. Defaults to 1000.
    
        Returns:
            str: Markdown table of average prices by collection, or error message if the query fails.
        """
        try:
            data = get_latest_result(5140470, limit=limit)
            df = pd.DataFrame(data)
            return df.to_markdown()
        except Exception as e:
            return str(e)  
  • main.py:87-87 (registration)
    The @mcp.tool() decorator registers the get_average_price_by_collection function as an MCP tool.
    @mcp.tool()
  • main.py:21-44 (helper)
    Helper function used by the tool to fetch latest results from a specified Dune Analytics query.
    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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions that the tool returns a markdown table or error message, which adds some context about output format. However, it lacks details on critical behavioral traits like rate limits, authentication needs, data freshness, or whether it's a read-only operation (implied by 'Retrieve' but not explicit). For a tool with no annotations, this is a significant gap.

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 purpose stated clearly in the first sentence. The Args and Returns sections are structured efficiently, though the 'Returns' section could be more concise (e.g., by omitting 'or error message if the query fails' if errors are assumed). Overall, it avoids unnecessary verbosity.

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 (1 parameter, no output schema, no annotations), the description is somewhat complete but has gaps. It covers the basic purpose and parameter, and hints at output format. However, it lacks details on behavioral aspects and usage context, which are important for effective tool selection and invocation. Without annotations or output schema, more comprehensive guidance would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds minimal semantics beyond the input schema. It explains that 'limit' is 'Maximum number of rows to fetch from the query' and defaults to 1000, which matches the schema's default value. However, with 0% schema description coverage, the description doesn't fully compensate by providing details like valid ranges or implications of the limit parameter. The baseline is 3 since it adds some value but not enough to overcome the low coverage.

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 average selling price for NFT collections.' It specifies the verb ('Retrieve') and resource ('average selling price for NFT collections'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_daily_sales_by_collection' or 'get_daily_trading_volume_by_collection', which also involve collection data but focus on different metrics.

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 contexts where this tool is preferred, such as for price analysis rather than sales volume or trader metrics. Without such guidance, users must infer usage based on the tool name and description alone.

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/nft-analytics-mcp'

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