whale-insights

live_stats

Read-onlyIdempotent

Get live activity counters — whale moves today, smart-money wallets active, golden alerts (10s cache) — Live activity snapshot for the platform (real recent counts, no fabricated floors). Cached ~10s. Response includes meta.updatedAt and meta.cacheAgeSeconds (derived from the underlying whale-copy-signals cache timestamp; 0 when the cache is cold).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`meta`	No	Response freshness metadata. 10s cache; check `meta.cacheAgeSeconds` for exact age.
`attribution`	No
`activeAlerts`	No
`whaleMovesToday`	No
`smartMoneyWallets`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "activeAlerts": {
+      "type": "number"
+    },
+    "attribution": {
+      "$ref": "#/components/schemas/Attribution"
+    },
+    "meta": {
+      "description": "Response freshness metadata. 10s cache; check `meta.cacheAgeSeconds` for exact age.",
+      "properties": {
+        "cacheAgeSeconds": {
+          "description": "Seconds since the cache was last populated. 0 means just refreshed.",
+          "type": "integer"
+        },
+        "updatedAt": {
+          "description": "ISO timestamp of the underlying whale-signals cache.",
+          "format": "date-time",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "smartMoneyWallets": {
+      "type": "number"
+    },
+    "whaleMovesToday": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedJun 17, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description adds meaningful behavioral detail: a ~10s cache, a claim of 'real recent counts, no fabricated floors,' and explanation of returned meta fields, including cacheAgeSeconds. This goes well beyond what annotations already declare and helps the agent understand freshness and trustworthiness.

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 compact and front-loaded: the core purpose appears first, followed by caching and response metadata. Each sentence adds distinct information without padding or redundancy, and the internal details are relevant to an agent's decision-making.

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, cached snapshot tool with an output schema, the description covers key operational traits: cache behavior, response freshness fields, and data authenticity. No additional guidance is necessary for a correct call, since no parameters or prerequisites exist.

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 description has no parameter semantics to explain. The baseline for 0-parameter tools is 4, and the description's focus on output metadata is appropriate and sufficient.

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 uses a specific verb ('Get') and names concrete resources ('whale moves today, smart-money wallets active, golden alerts'), making the tool's scope immediately clear. It also frames the tool as a 'live activity snapshot for the platform,' which distinguishes it from historical or summary tools in the sibling list.

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

Usage Guidelines3/5

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

Usage context is implied through 'Live activity snapshot' and 'real recent counts,' suggesting this is the real-time counter tool rather than a historical or aggregated view. However, it does not explicitly name alternatives or state when-not-to-use it, which matters given many nearby siblings like whale_activity, golden_alerts_snapshot, and platform_stats.

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?