whale-insights

whale_score_history

Read-onlyIdempotent

Get daily whale score history — top tracked whale wallets ranked by composite score (win rate + avg return) over up to 90 days — Daily historical composite scores for tracked whale wallets. One row per wallet per day: wallet address, chain, label, composite score (0-100), win rate, average return %, and sample count. Only wallets with ≥5 resolved signals receive a score (honest, never fabricated). Filter by ?chain= for a single chain. Useful for tracking smart-money wallet performance trends. DB-backed, 5-min cache. Powered by whale_score_daily table (365d retention, permanent monthly archive). — Use this for daily historical data; use the corresponding live snapshot tool for current conditions and the monthly tool for long-term trends.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No	Number of days of history to return (1–90, default 30).
`chain`	No	Optional chain filter (ETH, BTC, SOL, BSC, ARB, etc.). Returns all chains when omitted.

Output Schema

TableJSON Schema

Name	Required	Description
`days`	No
`chain`	No	Chain filter applied (null = all chains).
`total`	No
`history`	No
`updatedAt`	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"
+    },
+    "chain": {
+      "description": "Chain filter applied (null = all chains).",
+      "nullable": true,
+      "type": "string"
+    },
+    "days": {
+      "type": "number"
+    },
+    "history": {
+      "items": {
+        "properties": {
+          "avgReturn": {
+            "description": "Average return % across resolved signals. Null when < 5 samples.",
+            "nullable": true,
+            "type": "number"
+          },
+          "chain": {
+            "description": "Blockchain chain (ETH, BTC, SOL, BSC, etc.).",
+            "nullable": true,
+            "type": "string"
+          },
+          "date": {
+            "description": "YYYY-MM-DD snapshot date.",
+            "format": "date",
+            "type": "string"
+          },
+          "sampleCount": {
+            "description": "Number of resolved signals used for score calculation.",
+            "type": "integer"
+          },
+          "score": {
+            "description": "Composite whale score (0-100, requires ≥5 resolved signals).",
+            "maximum": 100,
+            "minimum": 0,
+            "type": "number"
+          },
+          "walletAddress": {
+            "description": "Blockchain wallet address.",
+            "type": "string"
+          },
+          "walletLabel": {
+            "description": "Human-readable wallet label.",
+            "nullable": true,
+            "type": "string"
+          },
+          "winRate": {
+            "description": "Win rate as a fraction (0.71 = 71%). Null when < 5 samples.",
+            "maximum": 1,
+            "minimum": 0,
+            "nullable": true,
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    },
+    "updatedAt": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedJul 18, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already mark this read-only, idempotent, and non-destructive, so the description adds useful behaviors beyond them: 5-min cache, DB-backed storage, 365-day retention with permanent monthly archive, and the scoring threshold of ≥5 resolved signals. These details help the agent reason about freshness and data coverage.

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 main purpose is front-loaded and nearly every clause carries useful information: row structure, scoring threshold, cache, retention, and usage routing. It is slightly repetitive around 'daily historical composite scores' but contains no real filler.

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 only two optional parameters, an output schema, and annotations, the description covers the data window, chain filtering, freshness, retention, and alternative-tool selection. Nothing an agent needs to correctly invoke this tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both parameters. The description mostly restates the chain filter and the 90-day cap, adding no new semantic meaning beyond what the schema provides.

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 starts with the specific verb+resource pair 'Get daily whale score history' and immediately defines the scope: top tracked whale wallets ranked by composite score over up to 90 days. This clearly differentiates it from monthly and live snapshot siblings by emphasizing daily historical granularity.

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?

It explicitly states when to use this tool ('Use this for daily historical data') and directs the agent to alternative tools for current conditions and long-term trends. This gives a clear decision rule without ambiguity.

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?