Skip to main content
Glama

Whale Dataset Statistics

whale_stats

Retrieve statistics on the whale wallet dataset, including total wallets tracked, chains covered, and last update timestamp. Free endpoint.

Instructions

Get statistics about the whale wallet dataset: total wallets tracked, chains covered, last updated timestamp. Free endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for whale_stats tool. Calls GET /api/v1/whales/stats and returns the stats JSON.
      async () => {
        const res = await apiGet<WhaleStatsResponse>("/api/v1/whales/stats");
    
        if (!res.ok) {
          return {
            content: [
              {
                type: "text" as const,
                text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
              },
            ],
            isError: true,
          };
        }
    
        return {
          content: [
            { type: "text" as const, text: JSON.stringify(res.data, null, 2) },
          ],
        };
      },
    );
  • TypeScript interface defining the shape of the API response for whale_stats (dataset, source, update_frequency, stats).
    interface WhaleStatsResponse {
      dataset: string;
      source: string;
      update_frequency: string;
      stats: Record<string, unknown>;
    }
  • Registration of whale_stats tool via server.registerTool with its metadata and handler.
    server.registerTool(
      "whale_stats",
      {
        title: "Whale Dataset Statistics",
        description:
          "Get statistics about the whale wallet dataset: total wallets tracked, " +
          "chains covered, last updated timestamp. Free endpoint.",
        inputSchema: {},
      },
      async () => {
        const res = await apiGet<WhaleStatsResponse>("/api/v1/whales/stats");
    
        if (!res.ok) {
          return {
            content: [
              {
                type: "text" as const,
                text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
              },
            ],
            isError: true,
          };
        }
    
        return {
          content: [
            { type: "text" as const, text: JSON.stringify(res.data, null, 2) },
          ],
        };
      },
    );
  • Helper function that constructs full URLs from path and optional query params (used by apiGet).
    function buildUrl(
      path: string,
      params?: Record<string, string | number | undefined>,
    ): string {
      const url = new URL(path, baseUrl);
      if (params) {
        for (const [k, v] of Object.entries(params)) {
          if (v !== undefined && v !== "") {
            url.searchParams.set(k, String(v));
          }
        }
      }
      return url.toString();
    }
  • HTTP GET client used by the handler to call the Verilex API.
    export async function apiGet<T = unknown>(
      path: string,
      params?: Record<string, string | number | undefined>,
    ): Promise<ApiResponse<T>> {
      const url = buildUrl(path, params);
    
      const headers: Record<string, string> = {
        Accept: "application/json",
        "User-Agent": "verilex-mcp-server/0.1.0",
      };
    
      // Forward x402 payment token if present in env (for paid endpoints)
      const paymentToken = process.env.VERILEX_PAYMENT_TOKEN;
      if (paymentToken) {
        headers["X-Payment-Token"] = paymentToken;
      }
    
      const res = await fetch(url, { headers });
      const data = (await res.json()) as T;
    
      const stale = res.headers.get("X-Data-Stale");
      const lastUpdated = res.headers.get("X-Data-Last-Updated");
      const ageSeconds = res.headers.get("X-Data-Age-Seconds");
    
      return {
        ok: res.ok,
        status: res.status,
        data,
        stale: stale === "true",
        lastUpdated: lastUpdated ?? undefined,
        ageSeconds: ageSeconds ? Number(ageSeconds) : undefined,
      };
    }
Behavior3/5

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

No annotations provided; description adds 'Free endpoint' but does not disclose read-only behavior, rate limits, or side effects. For a simple stats endpoint, the gap is small but present.

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?

Single sentence that directly states purpose and key data points, no excess words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter stats tool with no output schema, the description fully explains what is returned (three specific metrics), making it complete for its simplicity.

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?

No parameters in input schema; description adds no parameter info but lists returned fields, which is helpful. Baseline for 0 params is high, and the output context is beneficial.

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?

Clearly states it gets statistics about the whale wallet dataset, listing specific data points (wallets tracked, chains, timestamp), distinguishing it from sibling stats tools for other datasets.

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?

Mentions 'Free endpoint' implying no authentication cost, but does not explicitly state when to use this tool versus alternative stats tools for other datasets.

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/carrierone/verilexdata-mcp'

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