whale-insights

leverage_history

Read-onlyIdempotent

Get daily Leverage Radar market-level history — avg/max pressure score, setup score, assets in critical zone, dominant regime, Fear & Greed over up to 90 days — Daily historical Leverage Radar market aggregates. One row per day: average pressure score across 30 tracked assets, maximum single-asset pressure, average setup score, count of assets in critical zone (≥76), dominant market regime, Fear & Greed index, and top-pressure asset symbol. DB-backed, 30-min cache. Pro-only per-asset detail excluded — market-level only. — 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": {
+          "assetsInCritical": {
+            "description": "Count of assets with pressureScore ≥ 76 (critical/danger zone).",
+            "type": "integer"
+          },
+          "assetsInDangerZone": {
+            "description": "Count of assets with Danger Zone setup label.",
+            "type": "integer"
+          },
+          "avgPressureScore": {
+            "description": "Average pressure score across all tracked assets (0-100).",
+            "maximum": 100,
+            "minimum": 0,
+            "type": "number"
+          },
+          "avgSetupScore": {
+            "description": "Average setup score across tracked assets.",
+            "maximum": 100,
+            "minimum": 0,
+            "type": "number"
+          },
+          "date": {
+            "description": "YYYY-MM-DD snapshot date.",
+            "format": "date",
+            "type": "string"
+          },
+          "dominantRegime": {
+            "description": "Market regime detected for the day.",
+            "enum": [
+              "Bull",
+              "Bear",
+              "Sideways",
+              "Accumulation",
+              "Unknown"
+            ],
+            "type": "string"
+          },
+          "fearGreed": {
+            "description": "Platform Fear & Greed index for the day.",
+            "maximum": 100,
+            "minimum": 0,
+            "nullable": true,
+            "type": "integer"
+          },
+          "maxPressureScore": {
+            "description": "Highest single-asset pressure score of the day.",
+            "maximum": 100,
+            "minimum": 0,
+            "type": "number"
+          },
+          "topPressureSymbol": {
+            "description": "Ticker symbol of the highest-pressure asset.",
+            "nullable": true,
+            "type": "string"
+          },
+          "whaleBuyCount": {
+            "description": "Whale buy signals that day.",
+            "type": "integer"
+          },
+          "whaleSellCount": {
+            "description": "Whale sell signals that day.",
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    },
+    "updatedAt": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedJul 17, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already mark the tool read-only and idempotent, and the description adds substantial context: DB-backed storage, a 30-minute cache, one row per day, 30 tracked assets, the critical-zone threshold (≥76), and Pro-only per-asset detail exclusion. 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.

Conciseness4/5

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

Front-loaded with a clear summary and structured with concrete details, but slightly redundant: 'Daily historical Leverage Radar market aggregates' repeats the opening, and the aggregate list appears twice (once as a preview, once with specific values and threshold). Still compact and functional.

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?

For a one-parameter tool with no required params and a full output schema, the description covers data frequency, cache behavior, metric semantics, critical-zone threshold, scope limitations, and routing guidance. Nothing essential is 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 single `days` parameter already has complete schema coverage with range and default in the input schema. The description only lightly restates 'up to 90 days' and daily scope, adding no meaningful parameter semantics beyond the schema, so baseline 3 is appropriate.

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?

Names a specific verb and resource ('Get daily Leverage Radar market-level history') and enumerates the exact aggregates returned, including pressure scores, setup score, critical-zone count, regime, and Fear & Greed. It is clearly distinguishable from live-snapshot and monthly trend 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 closing sentence explicitly directs the agent to use this tool for daily historical data, a live snapshot tool for current conditions, and a monthly tool for long-term trends. However, it refers to those alternatives generically rather than naming the exact sibling tools, so the guidance is strong but slightly less precise.

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?