whale-data

Market snapshot

market_snapshot

Read-onlyIdempotent

One-call market state for a pair: last price, 24h stats, average funding rate, open interest and recent liquidation totals from the venues that publish them. On the free plans BTC answers in full and any other coin as a headline; a paid plan covers every streamed pair in full. Descriptive market data only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`coin`	No	Alias for pair.
`pair`	No	Trading pair, for example ETH/USD. A bare symbol like ETH is read as ETH/USD. Defaults to BTC/USD when omitted. On the free plans BTC answers in full and any other coin as a headline; a paid plan reaches every streamed pair. A pair this server does not stream comes back covered:false, and no plan adds it.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No	One line saying what the numbers cover, or why there are none. Read it before reporting any zero as a market reading.
`pair`	No	The pair this snapshot describes.
`price`	No	Last traded price.
`covered`	No	False when this server does not stream the pair at all. No plan adds it.
`funding`	No	average_rate across the exchanges that publish one, and exchange_count behind that average.
`available`	No	False when this lane could not answer: a producer is dark, the pair sits outside this plan, or the argument named something we do not carry. Absent or true means the numbers are a real reading, not a guess.
`stats_24h`	No	The 24h statistics block: open, high, low, close, change and volume.
`free_pairs`	No	The pairs a keyless connection can read, returned when the pair asked for is not one of them.
`vs_history`	No	Where funding and open interest sit against the same pair recorded days: a phrase, a band and how many days back the comparison reaches. Null under 30 recorded days.
`access_note`	No	What this connection could not return and what lifts it. Always pass this on to the user: it is the only place that information appears.
`open_interest_usd`	No	Open interest in dollars, summed across the exchanges that publish it.
`exchanges_streaming`	No	How many exchanges are currently streaming this pair.
`liquidations_recent`	No	Recent forced closes for this pair: count, total_usd, the long and short split in counts and dollars, and window_minutes, without which a count cannot be read. available:false here means no reading, not zero.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

changedInput schema / properties / pair / description

Previous value: -"Trading pair, for example ETH/USD. A bare symbol like ETH is read as ETH/USD. Defaults to BTC/USD when omitted. Keyless calls reach the free pairs only; a paid plan reaches every streamed pair. A pair this server does not stream comes back covered:false, and no plan adds it."New value: +"Trading pair, for example ETH/USD. A bare symbol like ETH is read as ETH/USD. Defaults to BTC/USD when omitted. On the free plans BTC answers in full and any other coin as a headline; a paid plan reaches every streamed pair. A pair this server does not stream comes back covered:false, and no plan adds it."

Changed1 schema field changedSep 2, 2026

changedInput schema / properties / pair / description

Previous value: -"Trading pair, for example ETH/USD. A bare symbol like ETH is read as ETH/USD. Defaults to BTC/USD when omitted. Keyless calls reach the free pairs only; a developer plan reaches every streamed pair. A pair this server does not stream comes back covered:false, and no plan adds it."New value: +"Trading pair, for example ETH/USD. A bare symbol like ETH is read as ETH/USD. Defaults to BTC/USD when omitted. Keyless calls reach the free pairs only; a paid plan reaches every streamed pair. A pair this server does not stream comes back covered:false, and no plan adds it."

Changed2 schema fields changedAug 13, 2026

addedInput schema / properties / pair / description

Added value: +"Trading pair, for example ETH/USD. A bare symbol like ETH is read as ETH/USD. Defaults to BTC/USD when omitted. Keyless calls reach the free pairs only; a developer plan reaches every streamed pair. A pair this server does not stream comes back covered:false, and no plan adds it."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "access_note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "What this connection could not return and what lifts it. Always pass this on to the user: it is the only place that information appears."
+    },
+    "available": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "False when this lane could not answer: a producer is dark, the pair sits outside this plan, or the argument named something we do not carry. Absent or true means the numbers are a real reading, not a guess."
+    },
+    "covered": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "False when this server does not stream the pair at all. No plan adds it."
+    },
+    "exchanges_streaming": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "How many exchanges are currently streaming this pair."
+    },
+    "free_pairs": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The pairs a keyless connection can read, returned when the pair asked for is not one of them."
+    },
+    "funding": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "average_rate across the exchanges that publish one, and exchange_count behind that average."
+    },
+    "liquidations_recent": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Recent forced closes for this pair: count, total_usd, the long and short split in counts and dollars, and window_minutes, without which a count cannot be read. available:false here means no reading, not zero."
+    },
+    "note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "One line saying what the numbers cover, or why there are none. Read it before reporting any zero as a market reading."
+    },
+    "open_interest_usd": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Open interest in dollars, summed across the exchanges that publish it."
+    },
+    "pair": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The pair this snapshot describes."
+    },
+    "price": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Last traded price."
+    },
+    "stats_24h": {
+      "description": "The 24h statistics block: open, high, low, close, change and volume."
+    },
+    "vs_history": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Where funding and open interest sit against the same pair recorded days: a phrase, a band and how many days back the comparison reaches. Null under 30 recorded days."
+    }
+  },
+  "type": "object"
+}

First observedAug 13, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description does not need to repeat safety. It adds valuable behavioral context about free vs. paid plan differences (BTC full vs. headline for others, and paid covers all streamed pairs) and the 'descriptive data only' nature. This goes beyond what annotations provide.

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 two sentences plus a short clause, tightly packed with relevant facts. The core purpose is front-loaded, and every sentence earns its place without filler.

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?

Given the presence of an output schema and low complexity (2 optional params), the description adequately covers the operation, plan limitations, and scope. It omits explicit usage scenarios, but those are handled under usage guidance; other essentials like error behavior are not needed due to schema coverage.

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%, with detailed descriptions for 'coin' as alias and 'pair' including default behavior, bare-symbol handling, and plan/covered semantics. The tool description does not add additional parameter meaning beyond the schema, so a baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool provides a market snapshot for a trading pair, enumerating the specific data points (last price, 24h stats, funding rate, open interest, liquidation totals). This is a specific verb+resource with listed fields. However, it does not explicitly differentiate from sibling tools like market_brief or market_overview, so it loses a point.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use this tool versus the many sibling market tools (market_brief, market_overview, market_digest, etc.). It mentions plan limitations but does not state scenarios for selection, exclusions, or alternatives. Usage context is only implied through 'one-call market state'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All whale-data 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?