Skip to main content
Glama

whale-insights

by com.cryptowhaleinsights

whale_activity

Get whale activity aggregated by chain and direction — movement COUNTS by day over 1-30 days (not individual transfers; use whale_movements for individual records with amounts) — Aggregated, bounded time-series of recorded whale movements across all 14 supported chains, sourced from our internal signal-history archive. Returns honest movement COUNTS grouped by chain, by money-flow direction (inflow/outflow/transfer/unknown), and by day over a recent window — no per-transaction detail, wallet addresses or explorer links (those stay subscriber-gated at /api/whale-history). Use ?window=N to set the look-back in days (1–30, default 7). Counts only; no USD volume is reported because the archive carries no structured per-move USD figure. Served from cache (no per-request cost). Cached ~5min.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
windowNoLook-back window in days (1–30, default 7). Values outside the range are clamped.

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavior: returns aggregated counts, no USD volume, served from cache with ~5min refresh, and limitations on data. No contradiction or hidden behaviors.

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?

Description is concise yet comprehensive, covering purpose, differentiation, limitations, parameter usage, and caching. The single paragraph is well-organized with front-loaded key points. Minor room for improvement (e.g., bullet points) but strong overall.

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?

Given low complexity (1 param, no output schema), the description fully covers all necessary aspects: what it returns, what it doesn't, how to use the parameter, and data source. No missing critical information.

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?

Schema covers 100% of parameters with description. The tool description adds extra semantics: clamping behavior for window values outside range. This goes beyond the schema, justifying a score above baseline 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?

Clearly states the tool returns aggregated whale movement counts by chain and direction over 1-30 days. Distinguishes from sibling whale_movements by specifying it provides counts, not individual transfers. The verb 'Get' and resource 'whale activity' are specific and clear.

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

Usage Guidelines5/5

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

Explicitly directs users to use whale_movements for individual records with amounts. Provides context on what is not available (per-transaction detail, wallet addresses, USD volume). Also notes caching behavior, aiding in appropriate invocation.

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