whale-insights

recent_whales

Read-onlyIdempotent

Get the latest 3 whale transfers right now — live snapshot across 14 chains (use whale_activity for counts, whale_movements for paginated archive) — The most recent on-chain whale movements detected across supported chains, each with an explorer-verifiable reference. 10-min cache; check meta.cacheAgeSeconds for exact age. meta.chainCount is the number of unique chains represented in the cache; meta.signalCount is the total cached signal count before the top-3 slice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`meta`	No	Response freshness metadata. 10-min cache; check `meta.cacheAgeSeconds` for exact age.
`whales`	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"
+    },
+    "meta": {
+      "description": "Response freshness metadata. 10-min cache; check `meta.cacheAgeSeconds` for exact age.",
+      "properties": {
+        "cacheAgeSeconds": {
+          "description": "Seconds since the whale-signals cache was last refreshed.",
+          "type": "integer"
+        },
+        "chainCount": {
+          "description": "Number of unique chains in the current cache.",
+          "type": "integer"
+        },
+        "signalCount": {
+          "description": "Total cached whale signals (before top-3 slice).",
+          "type": "integer"
+        },
+        "updatedAt": {
+          "description": "ISO timestamp of the underlying whale-signals cache.",
+          "format": "date-time",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "whales": {
+      "items": {
+        "properties": {
+          "amountUsd": {
+            "type": "number"
+          },
+          "chain": {
+            "type": "string"
+          },
+          "direction": {
+            "type": "string"
+          },
+          "explorerUrl": {
+            "format": "uri",
+            "type": "string"
+          },
+          "token": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedJun 17, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds valuable context beyond that: a 10-minute cache, the exact meta fields to check for cache age, chain count, and signal count, and the claim that each movement has an explorer-verifiable reference. This is rich and useful, though it does not detail every edge case, so not a 5.

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 front-loaded with the core purpose and includes all essential guidance in two sentences. It is slightly dense and has minor redundancy ('Get the latest 3 whale transfers' vs 'The most recent on-chain whale movements'), but every segment adds either scoping, alternatives, or meta-field explanation. It is well-structured and compact.

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?

For a zero-parameter read-only tool with an output schema present, the description is complete: it states the exact result count, chain scope, cache behavior, key meta fields, and sibling alternatives. An agent has everything needed to invoke this tool correctly without inspecting schemas further.

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 is empty and the baseline is 4. The description does not need to explain parameter semantics, but it still adds meaning by documenting the meta return fields. No deduction is warranted for lack of parameter detail.

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 specific verb and resource: 'Get the latest 3 whale transfers right now — live snapshot across 14 chains'. It clearly distinguishes itself from siblings by naming whale_activity and whale_movements as alternatives for different needs. An agent can immediately identify what this tool returns and how it differs from nearby tools.

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?

The description explicitly tells the agent when to use alternatives: 'use whale_activity for counts, whale_movements for paginated archive'. This provides clear routing guidance and prevents misuse. It also characterizes this tool as a live, bounded snapshot, making the usage context unambiguous.

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?