Skip to main content
Glama

Lookup Whale Wallet

lookup_whale

Retrieve balance history, token holdings, recent transactions, and PnL metrics for any whale wallet address. Get on-chain analytics with a single query.

Instructions

Get full detail for a single whale wallet by address. Returns balance history, token holdings, recent transactions, and PnL metrics. Cost: $0.02 per query. Source: On-chain analytics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesWallet address (e.g. 0x...)

Implementation Reference

  • The handler function for the lookup_whale tool. It accepts an address, calls apiGet to /api/v1/whales/:address, handles 404/errors, and returns wallet detail JSON.
    async ({ address }) => {
      const res = await apiGet<{ dataset: string; data: Record<string, unknown> }>(
        `/api/v1/whales/${encodeURIComponent(address)}`,
      );
    
      if (!res.ok) {
        const msg =
          res.status === 404
            ? `Whale wallet ${address} not found.`
            : `API error (${res.status}): ${JSON.stringify(res.data)}`;
        return {
          content: [{ type: "text" as const, text: msg }],
          isError: res.status !== 404,
        };
      }
    
      const warn = stalenessWarning(res);
      return {
        content: [
          { type: "text" as const, text: `${warn}${JSON.stringify(res.data.data, null, 2)}` },
        ],
      };
    },
  • Registration call for lookup_whale including title, description, and inputSchema (zod string for address).
    server.registerTool(
      "lookup_whale",
      {
        title: "Lookup Whale Wallet",
        description:
          "Get full detail for a single whale wallet by address. Returns balance history, " +
          "token holdings, recent transactions, and PnL metrics. " +
          "Cost: $0.02 per query. Source: On-chain analytics.",
        inputSchema: {
          address: z
            .string()
            .describe("Wallet address (e.g. 0x...)"),
        },
      },
  • The server.registerTool('lookup_whale', ...) call that registers the tool with the MCP server.
    server.registerTool(
      "lookup_whale",
      {
        title: "Lookup Whale Wallet",
        description:
          "Get full detail for a single whale wallet by address. Returns balance history, " +
          "token holdings, recent transactions, and PnL metrics. " +
          "Cost: $0.02 per query. Source: On-chain analytics.",
        inputSchema: {
          address: z
            .string()
            .describe("Wallet address (e.g. 0x...)"),
        },
      },
      async ({ address }) => {
        const res = await apiGet<{ dataset: string; data: Record<string, unknown> }>(
          `/api/v1/whales/${encodeURIComponent(address)}`,
        );
    
        if (!res.ok) {
          const msg =
            res.status === 404
              ? `Whale wallet ${address} not found.`
              : `API error (${res.status}): ${JSON.stringify(res.data)}`;
          return {
            content: [{ type: "text" as const, text: msg }],
            isError: res.status !== 404,
          };
        }
    
        const warn = stalenessWarning(res);
        return {
          content: [
            { type: "text" as const, text: `${warn}${JSON.stringify(res.data.data, null, 2)}` },
          ],
        };
      },
    );
  • src/index.ts:49-59 (registration)
    The registerWhaleTools(server) call in the main server setup that wires up all whale tools including lookup_whale.
    registerWhaleTools(server);
    registerLabelTools(server);
    registerHolderTools(server);
    registerDexTools(server);
    registerContractTools(server);
    registerPmTools(server);
    registerPmArbTools(server);
    registerPmResolutionTools(server);
    registerEconTools(server);
    registerPmMicroTools(server);
  • The stalenessWarning helper used inside the handler to prepend a stale-data warning if applicable.
    /** Build a staleness warning string if the data is stale, or empty string. */
    export function stalenessWarning(res: ApiResponse): string {
      if (!res.stale) return "";
      const parts = ["[STALE DATA]"];
      if (res.lastUpdated) parts.push(`Last updated: ${res.lastUpdated}`);
      if (res.ageSeconds != null) parts.push(`Age: ${res.ageSeconds}s`);
      return parts.join(" ") + "\n\n";
    }
Behavior4/5

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

With no annotations, the description provides behavioral context: cost ($0.02 per query) and data source (on-chain analytics). It omits read-only hint but the operation is clearly a read query.

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 three sentences that efficiently deliver purpose, return data, cost, and source. No fluff; every sentence adds value.

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?

The description lists return fields and cost, adequate for a simple lookup. It could mention potential rate limits or authentication needs but is generally complete given the single parameter.

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% and the parameter description in the schema is clear. The tool description does not add further semantics beyond the schema, earning a baseline score of 3.

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 specifies the verb 'Get full detail', the resource 'single whale wallet', and enumerates the returned data (balance history, token holdings, recent transactions, PnL metrics). This distinguishes it from siblings like 'whale_stats' or 'whale_changes'.

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

Usage Guidelines4/5

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

The description implies usage when a detailed single-wallet view is needed and mentions a cost factor. However, it lacks explicit guidance on when not to use or alternatives among sibling whale 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/carrierone/verilexdata-mcp'

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