whale-insights

platform_stats

Read-onlyIdempotent

Get canonical platform metrics — tracked wallets, chains, win rate, BTC benchmark — Canonical platform metrics: tracked wallets, chains, tokens, tools, languages, supported chain list, plus a safe aggregate performance subset (win rate, average return, BTC benchmark). Cached ~60s. Response includes meta.updatedAt (ISO timestamp of when the response was generated).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`live`	No
`meta`	No	Response freshness metadata.
`chains`	No
`chainList`	No
`freeTools`	No
`languages`	No
`updatedAt`	No
`attribution`	No
`dataSources`	No
`performance`	No	Aggregate signal performance metrics.
`tokensTracked`	No
`trackedWallets`	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"
+    },
+    "chainList": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "chains": {
+      "type": "number"
+    },
+    "dataSources": {
+      "type": "number"
+    },
+    "freeTools": {
+      "type": "number"
+    },
+    "languages": {
+      "type": "number"
+    },
+    "live": {
+      "type": "object"
+    },
+    "meta": {
+      "description": "Response freshness metadata.",
+      "properties": {
+        "updatedAt": {
+          "description": "ISO timestamp of when the response was generated.",
+          "format": "date-time",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "performance": {
+      "description": "Aggregate signal performance metrics.",
+      "properties": {
+        "avgBtcBenchmark": {
+          "description": "Average BTC price change over the same holding windows as the resolved signals (%). Null when not enough data.",
+          "nullable": true,
+          "type": "number"
+        },
+        "avgReturn": {
+          "description": "Average return across all resolved signals (%).",
+          "type": "number"
+        },
+        "dataStartedAt": {
+          "description": "ISO timestamp of the oldest resolved signal.",
+          "format": "date-time",
+          "nullable": true,
+          "type": "string"
+        },
+        "losses": {
+          "description": "Number of losing resolved signals.",
+          "type": "number"
+        },
+        "totalResolved": {
+          "description": "Total number of signals with a resolved outcome.",
+          "type": "number"
+        },
+        "totalSignalCount": {
+          "description": "All-time signal count (including unresolved).",
+          "type": "number"
+        },
+        "winRate": {
+          "description": "Percentage of resolved signals that were profitable (0–100).",
+          "type": "number"
+        },
+        "wins": {
+          "description": "Number of winning resolved signals.",
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "tokensTracked": {
+      "type": "number"
+    },
+    "trackedWallets": {
+      "type": "number"
+    },
+    "updatedAt": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedJun 17, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already mark it read-only, idempotent, open-world, and non-destructive. The description adds meaningful context about caching ('Cached ~60s') and the response's `meta.updatedAt` timestamp, going beyond the structured fields. No contradiction found.

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?

Front-loaded with the core action and metric categories; the cache and timestamp details are relevant and placed at the end. Minor redundancy—'Canonical platform metrics' appears twice—keeps it from being perfectly concise.

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?

With no parameters, rich annotations, and an output schema, the description covers the remaining needed context: caching behavior, response freshness, and metric scope. It doesn't explain how to interpret win rate or BTC benchmark, but the output schema and 'safe aggregate performance subset' wording make that acceptable.

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 and schema coverage is 100%, so there is no parameter burden on the description. The description's enumeration of returned metric categories still adds useful semantic context by clarifying what the no-argument call returns.

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?

Opens with a specific verb-resource pair, 'Get canonical platform metrics', and enumerates the exact metric categories (tracked wallets, chains, win rate, BTC benchmark). This makes it clear this is the platform-wide aggregate metrics tool and distinguishes it from sibling analytics tools by scope.

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?

The word 'canonical' and the explicit metric list imply this is the go-to for platform-level aggregate stats, and 'safe aggregate performance subset' hints at a cautious choice. However, it never names alternative siblings like live_stats or status, nor does it state when not to use this tool.

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?