Skip to main content
Glama

Whale Movements

whale_movements

Monitor whale wallets for large balance changes across multiple blockchains to detect significant inflows, outflows, and transfers that may signal market moves.

Instructions

Get large balance changes across whale wallets. Shows significant inflows, outflows, and transfers that may signal market moves. Cost: $0.04 per query. Source: On-chain analytics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoFilter by blockchain network
min_usdNoMinimum movement size in USD
tokenNoFilter by token symbol
hoursNoLookback period in hours (default 24, max 168)
limitNoMaximum results (default 25)

Implementation Reference

  • The handler for the 'whale_movements' tool. Calls GET /api/v1/whales/movements with optional filters (chain, min_usd, token, hours, limit) and returns the response as text.
    // ── Whale movements ───────────────────────────────────────────────────
    
    server.registerTool(
      "whale_movements",
      {
        title: "Whale Movements",
        description:
          "Get large balance changes across whale wallets. Shows significant inflows, " +
          "outflows, and transfers that may signal market moves. " +
          "Cost: $0.04 per query. Source: On-chain analytics.",
        inputSchema: {
          chain: z
            .enum(["ethereum", "arbitrum", "polygon", "base", "bsc"])
            .optional()
            .describe("Filter by blockchain network"),
          min_usd: z
            .number()
            .optional()
            .describe("Minimum movement size in USD"),
          token: z
            .string()
            .optional()
            .describe("Filter by token symbol"),
          hours: z
            .number()
            .int()
            .min(1)
            .max(168)
            .optional()
            .describe("Lookback period in hours (default 24, max 168)"),
          limit: z
            .number()
            .int()
            .min(1)
            .max(100)
            .optional()
            .describe("Maximum results (default 25)"),
        },
      },
      async ({ chain, min_usd, token, hours, limit }) => {
        const res = await apiGet<WhaleQueryResponse>("/api/v1/whales/movements", {
          chain,
          min_usd,
          token,
          hours: hours ?? 24,
          limit: limit ?? 25,
        });
    
        if (!res.ok) {
          return {
            content: [
              {
                type: "text" as const,
                text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
              },
            ],
            isError: true,
          };
        }
    
        const { count, data } = res.data;
        const warn = stalenessWarning(res);
        const summary = `${warn}Found ${count} whale movement(s).`;
        const json = JSON.stringify(data, null, 2);
    
        return {
          content: [{ type: "text" as const, text: `${summary}\n\n${json}` }],
        };
      },
  • Zod input schema for whale_movements: optional chain (enum), min_usd (number), token (string), hours (int 1-168), limit (int 1-100).
    inputSchema: {
      chain: z
        .enum(["ethereum", "arbitrum", "polygon", "base", "bsc"])
        .optional()
        .describe("Filter by blockchain network"),
      min_usd: z
        .number()
        .optional()
        .describe("Minimum movement size in USD"),
      token: z
        .string()
        .optional()
        .describe("Filter by token symbol"),
      hours: z
        .number()
        .int()
        .min(1)
        .max(168)
        .optional()
        .describe("Lookback period in hours (default 24, max 168)"),
      limit: z
        .number()
        .int()
        .min(1)
        .max(100)
        .optional()
        .describe("Maximum results (default 25)"),
    },
  • Registration of 'whale_movements' tool via server.registerTool() within registerWhaleTools() function.
    server.registerTool(
      "whale_movements",
      {
        title: "Whale Movements",
        description:
          "Get large balance changes across whale wallets. Shows significant inflows, " +
          "outflows, and transfers that may signal market moves. " +
          "Cost: $0.04 per query. Source: On-chain analytics.",
        inputSchema: {
          chain: z
            .enum(["ethereum", "arbitrum", "polygon", "base", "bsc"])
            .optional()
            .describe("Filter by blockchain network"),
          min_usd: z
            .number()
            .optional()
            .describe("Minimum movement size in USD"),
          token: z
            .string()
            .optional()
            .describe("Filter by token symbol"),
          hours: z
            .number()
            .int()
            .min(1)
            .max(168)
            .optional()
            .describe("Lookback period in hours (default 24, max 168)"),
          limit: z
            .number()
            .int()
            .min(1)
            .max(100)
            .optional()
            .describe("Maximum results (default 25)"),
        },
      },
      async ({ chain, min_usd, token, hours, limit }) => {
        const res = await apiGet<WhaleQueryResponse>("/api/v1/whales/movements", {
          chain,
          min_usd,
          token,
          hours: hours ?? 24,
          limit: limit ?? 25,
        });
    
        if (!res.ok) {
          return {
            content: [
              {
                type: "text" as const,
                text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
              },
            ],
            isError: true,
          };
        }
    
        const { count, data } = res.data;
        const warn = stalenessWarning(res);
        const summary = `${warn}Found ${count} whale movement(s).`;
        const json = JSON.stringify(data, null, 2);
    
        return {
          content: [{ type: "text" as const, text: `${summary}\n\n${json}` }],
        };
      },
    );
  • src/index.ts:49-49 (registration)
    Top-level registration of all whale tools (including whale_movements) in the MCP server.
    registerWhaleTools(server);
  • HTTP GET helper that the handler uses to call /api/v1/whales/movements on 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,
      };
    }
Behavior2/5

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only notes cost and a vague 'significant' threshold, but fails to define 'whale', describe data sorting, pagination, or rate limits. Minimal insight beyond the basic purpose.

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?

Two clear sentences plus a cost/source note. Information is front-loaded and efficient. However, the cost detail, while useful, could be considered extraneous as it is not standard for tool descriptions.

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

Completeness2/5

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

Given no output schema and no annotations, the description is too sparse. It does not explain what a 'whale wallet' is, whether results are sorted, or how pagination works. For a tool with 5 parameters, this leaves significant gaps.

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?

Schema coverage is 100%, so the description adds little beyond what the schema already provides. The term 'large' loosely relates to min_usd, but no new constraints or examples are given. Baseline score is appropriate.

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 tool retrieves 'large balance changes across whale wallets' and describes the type of data (inflows, outflows, transfers). It distinguishes from sibling tools like whale_changes and whale_stats by specifying 'large' and 'whale wallets'.

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 explicit guidance on when to use this tool versus the many sibling whale-related tools (e.g., whale_changes, whale_stats). It mentions cost and source but no decision criteria or exclusions.

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