Skip to main content
Glama

whale-insights

by com.cryptowhaleinsights

whale_movements

Public whale movements archive — paginated 1-year history (no auth, MCP-compatible) — Returns a paginated archive of large whale on-chain movements recorded in the CryptoWhaleInsights signal-history database, covering up to 1 year (365 days). This is the public, unauthenticated counterpart to the authenticated /api/whale-history endpoint: it omits the explorerUrl field (Pro-only). AI agents can use this to analyse historical on-chain flow direction (inflow/outflow/transfer) across 14 chains without any credentials. Supported chains (chain filter values): BTC, ETH, SOL, BSC, BASE, ARB, POLYGON, TON, SUI, HYPE, TRX, SEI, INJ, APT. Supported directions (direction filter values): inflow, outflow, transfer. Keyword search: use ?q= to filter by token name, signal summary, or wallet label (case-insensitive, max 100 chars). Example: ?q=USDT returns only moves mentioning USDT; ?q=ETH+Whale+%237 returns moves by that wallet label. USD filter: use ?minUsd= to only return movements at or above that real USD value, e.g. ?

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoKeyword search (case-insensitive, max 100 chars). Matches against token name, signal summary, or wallet label. Example: q=USDT returns moves mentioning USDT; q=ETH+Whale+%237 returns moves by that wallet label.
pageNoPage number (1-indexed, default 1).
chainNoFilter by chain. Valid values: BTC, ETH, SOL, BSC, BASE, ARB, POLYGON, TON, SUI, HYPE, TRX, SEI, INJ, APT. Default: all chains.
periodNoTime window: 7d | 30d | 90d | 365d (default 90d). Use 365d to retrieve up to 1 year of history.90d
directionNoFilter by flow direction: inflow | outflow | transfer. Default: all directions.

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description covers key behaviors: no auth required, public endpoint, paginated, 1-year limit, omission of explorerUrl, and lists supported chains and directions. This fully informs the agent of what to expect.

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 well-structured: starts with overall purpose, then details supported values, then examples. It is fairly long but every sentence adds value; slight redundancy in listing chain values again after schema.

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?

The description lacks explicit response format details (e.g., pagination metadata, specific fields returned) despite having no output schema. It mentions omission of explorerUrl but does not define what is included. For a tool with 5 parameters, this is a notable gap.

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?

All 5 parameters have schema descriptions (100% coverage), so baseline is 3. The description adds value by providing example queries (q=USDT, q=ETH+Whale+%237) and clarifying that period 365d retrieves up to 1 year of history, which goes beyond schema.

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 returns a paginated archive of whale on-chain movements with a 1-year limit. It specifies the verb 'returns' and resource, and distinguishes from siblings like 'recent_whales' by noting it's the public, unauthenticated counterpart.

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 explicitly says 'AI agents can use this to analyse historical on-chain flow direction... without any credentials' and mentions it's the public counterpart to the authenticated endpoint (implying when not to use). However, it does not explicitly name sibling tools as alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All whale-insights toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools have distinct purposes, but there are a few pairs with overlapping boundaries (e.g., analysts_signals vs analysts_signals_all, whale_movements vs whale_movements_summary) that could cause minor confusion.

Naming Consistency4/5

Naming is predominantly snake_case and descriptive, with minor inconsistencies in plural/singular forms (e.g., 'analysts' vs 'analyst_archive'). Overall pattern is stable.

Tool Count2/5

With 55 tools, the server is quite heavy. While the scope is broad, many tools are history/monthly variants that could be combined, making the count feel inflated beyond what is ideal for a single server.

Completeness4/5

The tool set covers a wide range of crypto analytics domains (analysts, arbitrage, funding, whales, sentiment, etc.). Minor gaps exist (e.g., no direct token price endpoint), but overall it's a comprehensive surface.

Resources