whale-insights

whale_monthly_archive

Read-onlyIdempotent

Whale movements permanent monthly archive — Returns the permanent monthly archive of whale movement activity — one row per calendar month, aggregated from daily whale summaries before they are purged. This archive is never deleted and grows indefinitely, enabling AI agents to answer historical questions like 'in which month were whale movements highest?' across years of data. Each month includes: totalMoves (total whale signals), totalUsdValue (cumulative USD value), inflowCount/outflowCount (directional breakdown), daysInMonth, avgMovesPerDay. Months with fewer than 20 daily records are excluded. Data source: CryptoWhaleInsights own signal_history database (80+ wallets, 14 chains). No authentication required. 60 req/min. 5-min cache.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	No
`months`	No
`updatedAt`	No
`dataSource`	No
`attribution`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "attribution": {
+      "$ref": "#/components/schemas/Attribution"
+    },
+    "dataSource": {
+      "type": "string"
+    },
+    "months": {
+      "items": {
+        "properties": {
+          "avgMovesPerDay": {
+            "type": "number"
+          },
+          "daysInMonth": {
+            "type": "integer"
+          },
+          "inflowCount": {
+            "type": "integer"
+          },
+          "month": {
+            "description": "First day of the month (YYYY-MM-01, UTC).",
+            "format": "date",
+            "type": "string"
+          },
+          "outflowCount": {
+            "type": "integer"
+          },
+          "totalMoves": {
+            "type": "integer"
+          },
+          "totalUsdValue": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    },
+    "updatedAt": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedJun 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already mark the tool as read-only, open-world, and idempotent, and the description adds substantial behavioral context: the archive is never deleted and grows indefinitely, months with fewer than 20 daily records are excluded, the data source is specified, and rate limits plus cache duration are disclosed. This goes well beyond what annotations alone provide.

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 information-dense and each clause contributes useful guidance: purpose, use case, output fields, exclusion rule, data source, authentication, rate limit, and cache. A minor redundancy exists in the opening ('Whale movements permanent monthly archive — Returns the permanent monthly archive'), but it is short and does not obscure the content.

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?

Given the tool has no parameters, an output schema exists, and annotations cover safety semantics, the description supplies everything an agent needs to decide when and how to invoke it: historical purpose, row granularity, available fields, data source, exclusion rule, rate limit, and cache. Nothing essential is missing.

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?

The tool has zero parameters, so the input schema requires no clarification. The description goes beyond that by enumerating the returned month-level fields (totalMoves, totalUsdValue, inflowCount/outflowCount, daysInMonth, avgMovesPerDay), which helps the agent understand output semantics. With no parameters, a baseline of 4 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 opens with a clear verb and resource: 'Returns the permanent monthly archive of whale movement activity.' It further distinguishes this tool from related siblings by specifying one row per calendar month aggregated from daily whale summaries, and it explicitly frames the historical use case. The opening phrase is slightly redundant with the tool name, but the resource and scope are unmistakable.

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 clearly indicates when to use this tool: for historical questions across years of data, as in 'in which month were whale movements highest?' It does not explicitly name alternatives or state when not to use it, but the historical archive framing implicitly separates it from live or daily whale tools.

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

All whale-insights tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?