whale-insights

leverage_radar

Read-onlyIdempotent

Get current Leverage Radar snapshot — pressure scores, setup scores, top long/short setups, and market summary for 50 tracked assets — Public real-time snapshot of the Leverage Radar tool. Returns pressure score (0-100, how overleveraged each asset is) and setup score (0-100, how good a leveraged trade opportunity looks) for 50 tracked assets across majors, L2s, DeFi, and meme tokens. Includes market summary (overall bias, avg scores, Fear & Greed, market regime, whale buy/sell counts), top 5 long setups, top 5 short setups, and top 5 pressure alerts. Pro-only fields stripped: whale X multiplier, exact whale USD volumes, detailed setup factors, and Best Trade Now recommendation. 5-min cache. Supports ?window=1h|4h|12h (default 4h).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`window`	No	Trading window: 1h (scalp), 4h (swing, default), 12h (position).	4h

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`window`	No	Trading window used for computation.
`assetCount`	No	Total assets tracked (50).
`computedAt`	No
`disclaimer`	No
`attribution`	No
`windowHours`	No	Window in hours.
`marketSummary`	No
`topLongSetups`	No
`pressureAlerts`	No
`topShortSetups`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "assetCount": {
+      "description": "Total assets tracked (50).",
+      "type": "integer"
+    },
+    "attribution": {
+      "$ref": "#/components/schemas/Attribution"
+    },
+    "computedAt": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "disclaimer": {
+      "type": "string"
+    },
+    "marketSummary": {
+      "properties": {
+        "avgPressureScore": {
+          "description": "Average pressure score across all 50 tracked assets.",
+          "maximum": 100,
+          "minimum": 0,
+          "type": "number"
+        },
+        "avgSetupScore": {
+          "description": "Average setup quality score across all tracked assets.",
+          "maximum": 100,
+          "minimum": 0,
+          "type": "number"
+        },
+        "fearGreed": {
+          "description": "Platform Fear & Greed index (0=Extreme Fear, 100=Extreme Greed).",
+          "maximum": 100,
+          "minimum": 0,
+          "nullable": true,
+          "type": "integer"
+        },
+        "fearGreedLabel": {
+          "description": "Human-readable F&G classification.",
+          "nullable": true,
+          "type": "string"
+        },
+        "overallBias": {
+          "description": "Aggregated market bias derived from all scores.",
+          "enum": [
+            "bullish",
+            "bearish",
+            "neutral"
+          ],
+          "type": "string"
+        },
+        "regime": {
+          "description": "Current market regime (Bull/Bear/Sideways/Accumulation).",
+          "nullable": true,
+          "type": "string"
+        },
+        "whaleBuyCount": {
+          "description": "Whale buy signals in the selected window.",
+          "type": "integer"
+        },
+        "whaleSellCount": {
+          "description": "Whale sell signals in the selected window.",
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "note": {
+      "type": "string"
+    },
+    "pressureAlerts": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "topLongSetups": {
+      "items": {
+        "properties": {
+          "fundingRate": {
+            "description": "Current funding rate % (negative=shorts pay longs).",
+            "nullable": true,
+            "type": "number"
+          },
+          "pressureScore": {
+            "description": "Leverage pressure score — higher = more overleveraged (dangerous).",
+            "maximum": 100,
+            "minimum": 0,
+            "type": "number"
+          },
+          "priceChange24h": {
+            "description": "24h price change %.",
+            "nullable": true,
+            "type": "number"
+          },
+          "riskLevel": {
+            "description": "Risk classification.",
+            "enum": [
+              "low",
+              "medium",
+              "high",
+              "extreme"
+            ],
+            "type": "string"
+          },
+          "setupLabel": {
+            "description": "Decision label: Strong Long Setup, Weak Long Setup, Strong Short Setup, etc.",
+            "type": "string"
+          },
+          "setupScore": {
+            "description": "Setup quality score — higher = better trade opportunity.",
+            "maximum": 100,
+            "minimum": 0,
+            "type": "number"
+          },
+          "symbol": {
+            "description": "Ticker symbol.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "topShortSetups": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "window": {
+      "description": "Trading window used for computation.",
+      "enum": [
+        "1h",
+        "4h",
+        "12h"
+      ],
+      "type": "string"
+    },
+    "windowHours": {
+      "description": "Window in hours.",
+      "enum": [
+        1,
+        4,
+        12
+      ],
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

AddedJul 18, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds valuable behavioral context beyond that: the 5-minute cache, that this is the public tier with pro-only fields stripped, and that content is restricted to 50 assets. The only minor tension is calling it 'real-time' while noting a 5-min cache, but the cache is disclosed clearly.

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?

The description is dense but every sentence adds information: asset coverage, score meanings, market summary contents, stripped fields, cache duration, and window flexibility. It is slightly long but well-organized and free of filler.

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?

Given an output schema exists and only one optional param is present, the description covers everything an agent needs: what the snapshot contains, its asset universe, its limitations (pro fields stripped), freshness (5-min cache), and the window parameter. There are no critical gaps for invoking it correctly.

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?

Schema coverage is 100% and the only parameter, window, already has enum values, a default, and per-window descriptions. The description merely repeats 'Supports ?window=1h|4h|12h (default 4h)', adding no semantic value beyond the schema.

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 resource ('Leverage Radar snapshot'), uses a clear verb ('Get'), and enumerates the exact output: pressure scores, setup scores, top long/short setups, and a market summary for 50 assets. The emphasis on 'current' and 'real-time snapshot' distinguishes it from historical sibling tools such as leverage_history.

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?

It provides clear context: a public, current snapshot with a 5-minute cache, stripped pro-only fields, and a selectable window. However, it never explicitly names an alternative tool or states when NOT to use this tool, so it stops short of a 5.

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?