whale-insights

market_pulse_history

Read-onlyIdempotent

Get daily Market Pulse history — BUY/SELL/NEUTRAL verdict, confidence %, Fear & Greed, regime, whale buy ratio, leverage suggestion over up to 90 days — Daily historical Market Pulse verdict and confidence. One row per day: BUY/SELL/NEUTRAL verdict, confidence percentage, Fear & Greed score, market regime (Bull/Bear/Sideways/Accumulation), whale buy ratio (0-1), average leverage pressure score (0-100), and leverage suggestion. DB-backed, 5-min cache. Powered by market_pulse_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).

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": {
+          "avgPressureScore": {
+            "description": "Average leverage pressure score across tracked assets.",
+            "maximum": 100,
+            "minimum": 0,
+            "nullable": true,
+            "type": "number"
+          },
+          "confidence": {
+            "description": "Confidence percentage for the verdict (0-100).",
+            "maximum": 100,
+            "minimum": 0,
+            "type": "number"
+          },
+          "date": {
+            "description": "YYYY-MM-DD snapshot date.",
+            "format": "date",
+            "type": "string"
+          },
+          "fearGreedScore": {
+            "description": "Platform Fear & Greed index for the day.",
+            "maximum": 100,
+            "minimum": 0,
+            "nullable": true,
+            "type": "number"
+          },
+          "leverageSuggestion": {
+            "description": "Derived leverage level suggestion.",
+            "enum": [
+              "none",
+              "low",
+              "moderate",
+              "high"
+            ],
+            "nullable": true,
+            "type": "string"
+          },
+          "regime": {
+            "description": "Market regime detected for the day.",
+            "enum": [
+              "Bull",
+              "Bear",
+              "Sideways",
+              "Accumulation"
+            ],
+            "nullable": true,
+            "type": "string"
+          },
+          "verdict": {
+            "description": "Aggregated market verdict for the day.",
+            "enum": [
+              "BUY",
+              "SELL",
+              "NEUTRAL"
+            ],
+            "type": "string"
+          },
+          "whaleBuyRatio": {
+            "description": "Ratio of whale buy signals vs total signals (0=all sell, 1=all buy).",
+            "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

A3.9/5.0

Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description adds useful behavioral context: DB-backed storage, a 5-minute cache, 365-day retention with monthly archive, and one row per day. It does not 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.

Conciseness2/5

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

The description is repetitive: the first sentence already lists the returned fields, and the second sentence largely repeats BUY/SELL/NEUTRAL verdict and confidence. While the extra detail about cache/retention is useful, a more compact structure would serve the agent better.

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

Completeness4/5

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

The description covers what data is returned, the daily granularity, data source, caching, retention, and when to use alternatives. With an output schema present, this is substantially complete; only exact sibling tool names are 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?

The only parameter, days, is already described in the schema with default, minimum, and maximum. The description only reiterates 'up to 90 days' and adds no additional semantic meaning, so the high schema coverage carries the weight.

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?

Description begins with a specific verb-resource pair: 'Get daily Market Pulse history'. It enumerates the fields returned and explicitly differentiates this history tool from live/momentary and long-term trend siblings, leaving no ambiguity about what it does.

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?

Explicitly says to use this tool for daily historical data, the live snapshot tool for current conditions, and the monthly tool for long-term trends. It gives clear selection criteria but does not name the exact sibling tool(s), leaving minor routing effort to the agent.

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?