whale-insights

reports_index

Read-onlyIdempotent

Weekly reports index — titles, summaries and dates (public, MCP-compatible) — Returns a public index of the last 12 weekly Alpha reports: title, a short plain-text summary (≤300 characters), the publish date, and the week covered. Full report content (HTML in 5 languages) remains Pro-only on GET /api/content/weekly-reports. AI agents can use this endpoint to inform users about recent report topics and dates without any authentication. Response: { reports[], total, updatedAt }. Each report: id (string), title (string), summary (string, ≤300 chars), publishedAt (ISO-8601), weekOf (YYYY-MM-DD). No authentication required. Cached 1 hour (reports are generated weekly). 60 requests/min rate limit.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`total`	No	Number of reports returned (≤12).
`reports`	No	Weekly report metadata in reverse-chronological order (newest first). Maximum 12 entries.
`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"
+    },
+    "reports": {
+      "description": "Weekly report metadata in reverse-chronological order (newest first). Maximum 12 entries.",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Unique report ID, e.g. 'report-2026-W25'",
+            "type": "string"
+          },
+          "publishedAt": {
+            "description": "When the report was generated (ISO-8601).",
+            "format": "date-time",
+            "type": "string"
+          },
+          "summary": {
+            "description": "Plain-text summary extracted from the English report, truncated to 300 characters.",
+            "type": "string"
+          },
+          "title": {
+            "description": "English report title, e.g. 'Weekly Alpha Report — BTC breakout & ETH accumulation signals'",
+            "type": "string"
+          },
+          "weekOf": {
+            "description": "Start date of the covered week (YYYY-MM-DD), e.g. '2026-06-16'.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Number of reports returned (≤12).",
+      "type": "number"
+    },
+    "updatedAt": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedJun 24, 2026

TDQS

A4.7/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. The description adds critical behavioral details: no authentication required, caching for 1 hour, 60 requests/min rate limit, and that reports are generated weekly. These go beyond the annotations and fully inform the agent of operational constraints.

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 dense yet well-organized. It front-loads the core purpose, then lists fields, access constraints, caching, rate limits, and response schema. Every sentence adds value with no fluff, achieving high information density without being rambling.

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 tool has no input parameters and an output schema is described inline (response structure). The description covers the purpose, content, access, caching, rate limiting, and response format. Nothing an agent needs to correctly invoke and interpret the response 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?

There are zero parameters, so the baseline is 4. The description compensates by detailing the response structure (reports, total, updatedAt and each report's fields), which is valuable even though there are no inputs to explain.

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 clearly states the specific verb 'Returns' and the resource 'a public index of the last 12 weekly Alpha reports', listing the exact fields (title, summary, publish date, week covered). It also distinguishes itself from Pro-only content, which differentiates it from potential sibling archive tools.

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 gives clear context: it is public, requires no authentication, and is intended for agents to inform users about recent report topics and dates. It explicitly notes that full report content is Pro-only, implying this endpoint is for summaries. However, it does not explicitly name alternatives or state when not to use it, but the context is sufficient for most agents.

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?