whale-data

Options (BTC, ETH)

options

Read-onlyIdempotent

BTC or ETH options: open interest by strike, put/call balance, max pain per expiry, implied volatility and recent large option trades.

Input Schema

TableJSON Schema

Name	Required	Description
`coin`	No	BTC (default) or ETH.
`cursor`	No	Next page: the cursor from the previous answer.
`detail`	No	brief (default): the answer, key numbers and top rows. full: every row, paged with cursor.

Output Schema

TableJSON Schema

Name	Required	Description
`as_of`	No	Data time, ISO.
`caveat`	No	A real limit, when non-null.
`cursor`	No	Next page (detail full).
`delayed`	No	Set when not live.
`summary`	No	The answer in one sentence.
`as_of_ms`	No	Data time, Unix ms.
`available`	No	False: no data; note says why.
`truncated`	No	Rows held back; see trimmed.
`next_tools`	No	Follow-up calls {tool,args,why}.
`access_note`	No	What this connection could not return.

Schema Changelog

Changes observed during successful MCP inspections.

Changed35 schema fields changedSep 24, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +{}
```

changedInput schema / properties / coin / description

Previous value: -"BTC or ETH (the only coins Deribit lists options for). A pair like BTC/USD works too, the quote leg is dropped. Defaults to BTC."New value: +"BTC (default) or ETH."

addedInput schema / properties / cursor

Added value: +{
+  "description": "Next page: the cursor from the previous answer.",
+  "type": "string"
+}

addedInput schema / properties / detail

Added value: +{
+  "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor.",
+  "enum": [
+    "brief",
+    "full"
+  ],
+  "type": "string"
+}

removedInput schema / properties / pair

Removed value: -{
-  "description": "Alias for coin.",
-  "type": "string"
-}

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

addedOutput schema / properties / access_note

Added value: +{
+  "description": "What this connection could not return."
+}

addedOutput schema / properties / as_of

Added value: +{
+  "description": "Data time, ISO."
+}

addedOutput schema / properties / as_of_ms

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Data time, Unix ms."
+}

removedOutput schema / properties / available / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

changedOutput schema / properties / available / description

Previous value: -"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."New value: +"False: no data; note says why."

addedOutput schema / properties / available / type
```
Added value: +"boolean"
```

removedOutput schema / properties / callOiUsd

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Open interest sitting in calls (upside bets), in USD."
-}

addedOutput schema / properties / caveat

Added value: +{
+  "description": "A real limit, when non-null."
+}

removedOutput schema / properties / coin

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "The coin these options are for (BTC or ETH)."
-}

removedOutput schema / properties / coins_covered

Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "The coins options are carried for (BTC, ETH)."
-}

addedOutput schema / properties / cursor

Added value: +{
+  "description": "Next page (detail full)."
+}

addedOutput schema / properties / delayed

Added value: +{
+  "description": "Set when not live."
+}

removedOutput schema / properties / dvol

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Implied-vol index: how big a swing the market is pricing in. Lower is calmer."
-}

removedOutput schema / properties / expiries

Removed value: -{
-  "anyOf": [
-    {
-      "items": {},
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Open interest grouped by expiry date, with days to go."
-}

removedOutput schema / properties / gammaWalls

Removed value: -{
-  "anyOf": [
-    {
-      "items": {},
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "The strikes holding the most open interest, biggest first, with the call and put split. These often act as magnets into expiry."
-}

removedOutput schema / properties / maxPain

Removed value: -{
-  "anyOf": [
-    {
-      "items": {},
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Per near expiry, the strike where the most options expire worthless."
-}

addedOutput schema / properties / next_tools

Added value: +{
+  "description": "Follow-up calls {tool,args,why}.",
+  "items": {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / note

Removed value: -{
-  "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."
-}

removedOutput schema / properties / openInterestUsd

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Total open interest in USD across all listed options."
-}

removedOutput schema / properties / putCallRatio

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Put open interest divided by call open interest. Above ~1.15 is put-heavy, below ~0.7 is call-heavy."
-}

removedOutput schema / properties / putOiUsd

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Open interest sitting in puts (downside protection), in USD."
-}

removedOutput schema / properties / recentLargeTrades

Removed value: -{
-  "anyOf": [
-    {
-      "items": {},
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Large option buys and sells above a size floor, newest first. Deeper on a paid plan."
-}

removedOutput schema / properties / recentTradesTruncated

Removed value: -{
-  "anyOf": [
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "True when the large-trade list was shortened for a keyless caller."
-}

changedOutput schema / properties / summary / description

Previous value: -"The answer in one plain sentence, computed from the fields below. Open the reply with this, then let the numbers back it up. Null only when there was nothing to summarise."New value: +"The answer in one sentence."

addedOutput schema / properties / truncated

Added value: +{
+  "description": "Rows held back; see trimmed."
+}

removedOutput schema / properties / underlyingPrice

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Spot price of the coin, from the venue."
-}

removedOutput schema / properties / updatedAt

Removed value: -{
-  "anyOf": [
-    {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "number"
-        }
-      ]
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "When this snapshot was published."
-}

removedOutput schema / properties / venue

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Always Deribit."
-}

Changed2 schema fields changedSep 2, 2026

addedInput schema / properties / pair

Added value: +{
+  "description": "Alias for coin.",
+  "type": "string"
+}

changedOutput schema / properties / recentLargeTrades / description

Previous value: -"Large option buys and sells above a size floor, newest first. Deeper on a developer plan."New value: +"Large option buys and sells above a size floor, newest first. Deeper on a paid plan."

AddedSep 1, 2026

TDQS

A3.6/5.0

Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description itself adds no behavioral context such as pagination behavior, defaults, or side effects; it only lists data content, which does not go beyond 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.

Conciseness5/5

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

The description is a single, front-loaded sentence that packs the resource and the key delivered data fields with no filler or redundant wording. Every part earns its place.

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 full input schema, output schema, and annotations cover the calling contract well, and the description supplies the domain content. The only notable gap is explicit usage routing versus sibling tools, but that is already captured under the usage-guidelines dimension.

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 description coverage is 100%: coin, cursor, and detail are all documented in the schema, including defaults and the brief/full enum. The description adds no parameter-specific meaning beyond that, so the baseline of 3 applies.

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 the specific resource (BTC or ETH options) and enumerates exactly what data is provided: open interest by strike, put/call balance, max pain per expiry, implied volatility, and large trades. This clearly distinguishes it from sibling tools like orderbook or liquidations.

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

Usage Guidelines3/5

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

The description implies a clear use case for fetching BTC/ETH options data, but gives no explicit when-to-use versus when-not-to-use guidance and does not name any alternatives or exclusions. The context is clear but the routing guidance is only implicit.

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?