whale-insights

fear_greed_history

Read-onlyIdempotent

Get daily Fear & Greed score history — 0-100 score + Extreme Fear/Greed label per day over up to 180 days (use fear_greed_monthly for 2-year trends) — Daily historical Fear & Greed score and classification for the last N days (default 30, max 180). One row per day saved from the platform's 7-factor composite index. Useful for trend analysis and AI agent context. DB-backed, 5-min cache. — 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–180, default 30).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No
`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"
+    },
+    "days": {
+      "type": "number"
+    },
+    "history": {
+      "items": {
+        "properties": {
+          "classification": {
+            "description": "Text label for the score.",
+            "enum": [
+              "Extreme Fear",
+              "Fear",
+              "Neutral",
+              "Greed",
+              "Extreme Greed"
+            ],
+            "type": "string"
+          },
+          "date": {
+            "description": "YYYY-MM-DD snapshot date.",
+            "format": "date",
+            "type": "string"
+          },
+          "score": {
+            "description": "Composite Fear & Greed score (0=Extreme Fear, 100=Extreme Greed).",
+            "maximum": 100,
+            "minimum": 0,
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    },
+    "updatedAt": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedJun 26, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds useful non-obvious behavior: DB-backed storage, 5-minute caching, and that data comes from a 7-factor composite index. No contradiction with annotations exists.

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 essential purpose, but it contains redundancy: 'daily historical' appears twice, and 'one row per day' and the label details are repeated. It earns its place overall, but tighter editing would improve clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema covers return values, and the description provides data source, cache behavior, and use cases, which is mostly sufficient. However, the contradictory maximum-day value (180 in description vs 90 in schema) leaves the agent unable to determine the real boundary, creating a meaningful completeness gap.

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

Parameters2/5

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

Schema coverage is 100%, so the baseline is 3, and the description does add meaning by explaining the per-row output and default/max behavior. However, it introduces a harmful inconsistency: the description says 'max 180' and the schema's "days" property has "maximum": 90, while the schema description also says '1–180.' This directly confuses the parameter boundary and undermines reliable invocation.

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 names a specific verb ('Get'), a clear resource ('daily Fear & Greed score history'), and the return contents ('0-100 score + Extreme Fear/Greed label per day'). It also differentiates itself from nearby siblings by explicitly scoping to daily history over up to 180 days, distinguishing it from fear_greed_monthly and the live snapshot tool.

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 explicitly states when to use this tool: 'Use this for daily historical data', and names alternatives: 'use the corresponding live snapshot tool for current conditions and the monthly tool for long-term trends.' It also mentions usefulness for trend analysis, giving an agent clear selection criteria.

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?