whale-insights

analyst_summary_history

Read-onlyIdempotent

Get historical daily AI analyst summaries — query by date or by analyst+days (max 90 days; use analyst_daily_summary for today's data) — Returns a paginated history of daily AI analyst summaries. Query by specific date (?date=YYYY-MM-DD) to see all analyst summaries for one day, or by analystId (?analystId=chain_hawk&days=30) to get the last N days for one analyst. Maximum 90 days. Only shortSummary is returned (full commentary is Pro-only). Fields per record: analystId, analystName, summaryDate (YYYY-MM-DD), shortSummary, summaryAr, summaryHi, summaryZh, summaryRu, signalCount, confluenceScore, fearGreedScore, btcTrend. No auth required. 60 req/min. — 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
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No
`days`	No
`total`	No
`analystId`	No
`summaries`	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": {
+    "analystId": {
+      "nullable": true,
+      "type": "string"
+    },
+    "attribution": {
+      "$ref": "#/components/schemas/Attribution"
+    },
+    "date": {
+      "nullable": true,
+      "type": "string"
+    },
+    "days": {
+      "type": "number"
+    },
+    "summaries": {
+      "items": {
+        "description": "One daily summary record.",
+        "properties": {
+          "analystId": {
+            "description": "Analyst ID, e.g. chain_hawk",
+            "type": "string"
+          },
+          "analystName": {
+            "description": "Display name, e.g. ChainHawk",
+            "type": "string"
+          },
+          "btcTrend": {
+            "enum": [
+              "up",
+              "down",
+              "sideways"
+            ],
+            "nullable": true,
+            "type": "string"
+          },
+          "confluenceScore": {
+            "description": "Cross-analyst agreement 0-100",
+            "nullable": true,
+            "type": "number"
+          },
+          "fearGreedScore": {
+            "description": "Fear & Greed at generation time",
+            "nullable": true,
+            "type": "number"
+          },
+          "shortSummary": {
+            "description": "2-sentence AI commentary (English)",
+            "type": "string"
+          },
+          "signalCount": {
+            "description": "Signals generated that day",
+            "type": "integer"
+          },
+          "summaryAr": {
+            "description": "Arabic translation",
+            "nullable": true,
+            "type": "string"
+          },
+          "summaryDate": {
+            "description": "YYYY-MM-DD",
+            "format": "date",
+            "type": "string"
+          },
+          "summaryHi": {
+            "description": "Hindi translation",
+            "nullable": true,
+            "type": "string"
+          },
+          "summaryRu": {
+            "description": "Russian translation",
+            "nullable": true,
+            "type": "string"
+          },
+          "summaryZh": {
+            "description": "Chinese translation",
+            "nullable": true,
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    },
+    "updatedAt": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedJun 30, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Even though annotations already declare readOnly, idempotent, and non-destructive behavior, the description adds substantial context: pagination, 90-day limit, Pro-only full commentary, returned field list, no-auth requirement, and 60 req/min rate limit. None of these contradict the annotations.

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 long but information-dense, with the main purpose front-loaded and query patterns laid out clearly. There is minor redundancy between 'historical daily AI analyst summaries' and the closing 'Use this for daily historical data', but no wasted sentences.

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 empty input schema and the need to differentiate among many siblings, the description is complete: it covers query modes, limits, auth, rate limits, response fields, access restrictions, and alternatives. An agent has everything needed to call it correctly.

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

Parameters5/5

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

The input schema has zero properties, so the description fully carries parameter semantics. It documents query parameters including ?date=YYYY-MM-DD, ?analystId=...&days=30, and the 90-day cap, and even lists the fields returned per record. This goes 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 opens with a specific verb-resource pair ('Get historical daily AI analyst summaries') and gives exact query modes. It explicitly distinguishes itself from analyst_daily_summary, the monthly tool, and live snapshot tools, so an agent can tell it apart from siblings.

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 gives explicit when-to-use guidance: use for daily historical data, use analyst_daily_summary for today's data, the live snapshot tool for current conditions, and the monthly tool for long-term trends. It also states the 90-day maximum and the two query patterns.

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?