whale-insights

analyst_daily_summary

Read-onlyIdempotent

Get today's AI-generated commentary for all 10 analysts — 2-sentence summaries with signal count, confluence score, BTC trend (generated 9:00 UTC) — Returns today's AI-generated daily commentary for all 10 analyst personas. Summaries are generated each morning at 9:00 UTC using gpt-4o-mini based on the previous 24h of signals, Fear & Greed score, BTC trend, and cross-analyst confluence. Public endpoint — no authentication required. Only shortSummary is returned (2 sentences). Full commentary is available via the authenticated Pro endpoint /api/analysts/:id/daily-summary. Fields per analyst: analystId, analystName, summaryDate (YYYY-MM-DD), shortSummary, signalCount (signals in the past 24h), confluenceScore (0-100: % of other analysts with overlapping tokens in last 2h), fearGreedScore (0-100), btcTrend ('up'|'down'|'sideways'|null). Cached 30 minutes. Returns empty summaries array before 9:00 UTC on any given day. 60 req/min rate limit.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	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": {
+    "attribution": {
+      "$ref": "#/components/schemas/Attribution"
+    },
+    "summaries": {
+      "items": {
+        "description": "One daily summary per analyst.",
+        "properties": {
+          "analystId": {
+            "description": "Analyst slug, e.g. chain_hawk",
+            "type": "string"
+          },
+          "analystName": {
+            "description": "Display name, e.g. ChainHawk",
+            "type": "string"
+          },
+          "btcTrend": {
+            "description": "BTC 24h trend at generation time",
+            "enum": [
+              "up",
+              "down",
+              "sideways"
+            ],
+            "nullable": true,
+            "type": "string"
+          },
+          "confluenceScore": {
+            "description": "0-100: % of other analysts with overlapping tokens in the last 2h — higher = more cross-analyst agreement",
+            "nullable": true,
+            "type": "number"
+          },
+          "fearGreedScore": {
+            "description": "Market Fear & Greed score at time of generation (0=Extreme Fear, 100=Extreme Greed)",
+            "nullable": true,
+            "type": "number"
+          },
+          "shortSummary": {
+            "description": "2-sentence AI commentary on the analyst's day (public)",
+            "type": "string"
+          },
+          "signalCount": {
+            "description": "Number of signals this analyst generated in the past 24h",
+            "type": "integer"
+          },
+          "summaryDate": {
+            "description": "YYYY-MM-DD date of this summary",
+            "format": "date",
+            "type": "string"
+          },
+          "updatedAt": {
+            "format": "date-time",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    },
+    "updatedAt": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedJun 27, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, but the description goes well beyond that: generation time (9:00 UTC), model (gpt-4o-mini), no auth required, only shortSummary returned, caching (30 min), empty-array behavior before 9:00 UTC, and rate limit (60 req/min). This is rich behavioral disclosure with no contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the key verb and scope, but it repeats itself: 'Get today's AI-generated commentary' is restated as 'Returns today's AI-generated daily commentary', and '9:00 UTC' appears three times. The extra details are useful, but the redundancy makes it longer than necessary.

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?

The output schema exists, so return values are covered. The description adds everything else needed: timing (generated 9:00 UTC, empty before), caching (30 min), rate limit, auth status, and the exact fields returned. Nothing an agent needs to call this tool correctly is missing.

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 input schema has zero properties, so there are no parameters to document. Baseline 4 applies. The description appropriately spends its space on response fields and behavior instead of parameter semantics, which is exactly right for a no-input tool.

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 today's AI-generated commentary for all 10 analysts'. It specifies the exact scope (today's, all 10 analysts, 2-sentence summaries) and clearly distinguishes this from sibling tools like analyst_archive or analyst_summary_history, which cover historical data.

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

Usage Guidelines4/5

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

The description provides clear context: use for today's generated commentary, public endpoint, no auth, and it notes the fallback for full commentary via the authenticated Pro endpoint. It also gives timing constraints (empty before 9:00 UTC, cached 30 min). However, it does not explicitly name sibling tools as alternatives or state when to prefer them over this one.

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?