Skip to main content
Glama
kukapay

solana-launchpads-mcp

get_daily_graduates

Fetch daily graduate counts from Solana memecoin launchpads to track successful token sales and project completions by platform.

Instructions

Fetch the daily number of graduates from Solana memecoin launchpads.

This tool retrieves data from a Dune Analytics query and pivots it to show the number of
successful graduates (e.g., completed token sales or projects) per day by each platform.

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

Returns:
    str: A markdown-formatted table of daily graduates by platform, or an error message if the
        query fails.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Implementation Reference

  • main.py:75-98 (handler)
    The handler function for the 'get_daily_graduates' tool. Decorated with @mcp.tool() for registration. Fetches data from Dune Analytics query ID 5131612, processes it into a pivoted DataFrame by date and platform, sorts descending by date, and returns a markdown table. Falls back to error string on exception.
    @mcp.tool()
    def get_daily_graduates(limit: int = 1000) -> str:
        """
        Fetch the daily number of graduates from Solana memecoin launchpads.
    
        This tool retrieves data from a Dune Analytics query and pivots it to show the number of
        successful graduates (e.g., completed token sales or projects) per day by each platform.
    
        Args:
            limit (int, optional): Maximum number of rows to fetch from the Dune query. Defaults to 1000.
    
        Returns:
            str: A markdown-formatted table of daily graduates by platform, or an error message if the
                query fails.
        """
        try:
            data = get_latest_result(5131612, limit=limit)
            df = pd.DataFrame(data)
            df['block_date'] = pd.to_datetime(df['block_date']).dt.date
            pivot_df = df.pivot(index="block_date", columns="platform", values="daily_graduates")
            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 get_daily_graduates (and other tools) to fetch the latest results from a specified Dune Analytics query using the API, returning the rows as a list of dicts.
    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
  • main.py:75-75 (registration)
    The @mcp.tool() decorator registers the get_daily_graduates function as an MCP tool.
    @mcp.tool()
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well by disclosing key behaviors: it retrieves data from Dune Analytics, pivots it, and returns a markdown table or error message. It mentions the query might fail, adding context. However, it lacks details on rate limits, authentication needs, or data freshness, which could be important for an agent.

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 additional context in a second sentence, and then structured sections for Args 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.

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 (fetching and processing data from an external source), no annotations, and no output schema, the description is fairly complete. It explains what the tool does, the parameter, and the return format. However, it could improve by detailing error conditions or data sources more explicitly, but it covers the essentials well.

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 schema description coverage is 0%, so the description must compensate. It adds meaning by explaining the 'limit' parameter as 'Maximum number of rows to fetch from the Dune query' with a default of 1000, which clarifies its purpose beyond the schema's basic type and title. Since there is only one parameter, this is sufficient for good understanding.

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 verb 'fetch' and the resource 'daily number of graduates from Solana memecoin launchpads', specifying it retrieves data from Dune Analytics and pivots it to show graduates per day by platform. It distinguishes from siblings like 'get_daily_active_addresses' or 'get_daily_tokens_deployed' by focusing on graduates rather than addresses or tokens.

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

Usage Guidelines3/5

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

The description implies usage for fetching graduate data from launchpads, but does not explicitly state when to use this tool versus alternatives like 'get_daily_graduation_rate' (which might provide rates rather than counts). No exclusions or specific contexts are provided, leaving some ambiguity in 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/solana-launchpads-mcp'

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