Skip to main content
Glama

get_kpi_list

Fetch key performance indicators for Wormhole cross-chain protocol to analyze transaction volumes, asset flows, and chain activity metrics.

Instructions

Fetch a list of KPIs for Wormhole from Wormholescan API.

Returns:
    String representation of a pandas DataFrame containing Wormhole KPIs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.py:464-506 (handler)
    The handler function for the 'get_kpi_list' tool, decorated with @mcp.tool() which registers it with the MCP server. It fetches KPI data from the Wormholescan API, transforms it into a pandas DataFrame, and returns a markdown representation.
    # Define the get_kpi_list tool
    @mcp.tool()
    async def get_kpi_list() -> str:
        """
        Fetch a list of KPIs for Wormhole from Wormholescan API.
        
        Returns:
            String representation of a pandas DataFrame containing Wormhole KPIs
        """
        try:
            # Make API request
            async with httpx.AsyncClient() as client:
                response = await client.get(
                    f"{API_BASE}/api/v1/scorecards"
                )
                response.raise_for_status()
                
                # Parse JSON response
                data = response.json()
                
                # Transform data for DataFrame
                rows = [{
                    "24h_messages": data.get("24h_messages"),
                    "total_messages": data.get("total_messages"),
                    "total_tx_count": data.get("total_tx_count"),
                    "total_volume": data.get("total_volume"),
                    "tvl": data.get("tvl"),
                    "24h_volume": data.get("24h_volume"),
                    "7d_volume": data.get("7d_volume"),
                    "30d_volume": data.get("30d_volume")
                }]
                
                # Create DataFrame
                df = pd.DataFrame(rows)
                
                # Convert numeric columns
                for col in df.columns:
                    df[col] = pd.to_numeric(df[col], errors="coerce")
                
                return df.to_markdown(index=False)
                
        except Exception as e:
            return str(e)        
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the return format ('String representation of a pandas DataFrame'), which adds some behavioral context, but lacks details on error handling, rate limits, authentication needs, or data freshness. The description doesn't contradict annotations (none provided).

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 concise with two sentences: one stating the purpose and source, and another specifying the return format. It's front-loaded with the main action. However, the second sentence could be integrated more smoothly, and there's minor redundancy in specifying 'Wormhole' twice.

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 0 parameters and no output schema, the description is moderately complete. It covers the purpose and return format, but as a tool with no annotations, it should ideally include more behavioral context (e.g., data scope, limitations). The lack of usage guidelines and minimal transparency details leaves gaps for an AI agent to use it effectively.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details beyond the schema, but this is acceptable as there are no parameters. Baseline is 4 for 0 parameters, as the description doesn't need to compensate for missing schema info.

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 action ('Fetch') and resource ('list of KPIs for Wormhole'), specifying the source ('from Wormholescan API'). It distinguishes from siblings by focusing on KPIs rather than activity, money flow, corridors, assets, chain pairs, or symbols. However, it doesn't explicitly contrast with siblings like 'get_top_chain_pairs_by_num_transfers' which might also involve KPIs.

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. The description mentions fetching KPIs but doesn't specify scenarios, prerequisites, or exclusions. For example, it doesn't clarify if this is for general KPI overview versus detailed metrics available in other tools.

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

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