whale-data

Options intelligence (Deribit)

options

Read-onlyIdempotent

The options picture for BTC or ETH from Deribit: total open interest, the strikes holding the most of it (the walls, which act as magnets into expiry), the put/call balance, max pain per near expiry, the implied-vol regime (DVOL), and recent large option trades. Aggregate market structure, keyless; the large-trade feed deepens on a paid plan. Descriptive market data only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`coin`	No	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.
`pair`	No	Alias for coin.

Output Schema

TableJSON Schema

Name	Required	Description
`coin`	No	The coin these options are for (BTC or ETH).
`dvol`	No	Implied-vol index: how big a swing the market is pricing in. Lower is calmer.
`note`	No	One line saying what the numbers cover, or why there are none. Read it before reporting any zero as a market reading.
`venue`	No	Always Deribit.
`maxPain`	No	Per near expiry, the strike where the most options expire worthless.
`summary`	No	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.
`expiries`	No	Open interest grouped by expiry date, with days to go.
`putOiUsd`	No	Open interest sitting in puts (downside protection), in USD.
`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.
`callOiUsd`	No	Open interest sitting in calls (upside bets), in USD.
`updatedAt`	No	When this snapshot was published.
`gammaWalls`	No	The strikes holding the most open interest, biggest first, with the call and put split. These often act as magnets into expiry.
`putCallRatio`	No	Put open interest divided by call open interest. Above ~1.15 is put-heavy, below ~0.7 is call-heavy.
`coins_covered`	No	The coins options are carried for (BTC, ETH).
`openInterestUsd`	No	Total open interest in USD across all listed options.
`underlyingPrice`	No	Spot price of the coin, from the venue.
`recentLargeTrades`	No	Large option buys and sells above a size floor, newest first. Deeper on a paid plan.
`recentTradesTruncated`	No	True when the large-trade list was shortened for a keyless caller.

Schema Changelog

Changes observed during successful MCP inspections.

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.7/5.0

Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true, and destructve=false. The description adds worthwhile behavioral context: it is keyless, it is 'Descriptive market data only', and the large-trade feed deepens on a paid plan. No contradiction with the 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?

The description is compact, front-loaded with the resource and data contents, then adds auth and safety caveats in short declarative sentences. The parenthetical 'which act as magnets into expiry' is a little extra but still informative; overall no sentence is waste.

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 a rich output schema, full parameter schema coverage, and safety annotations, the description covers coins, exchange, data fields, auth model, paid-plan limitation, and descriptive nature. It is complete enough for an agent to invoke correctly, though it could have briefly noted when not to choose it among the many sibling market tools.

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%, so the baseline is 3. The schema already documents coin and pair, including that BTC/ETH are the only supported coins and that BTC is default. The tool description repeats 'BTC or ETH' but does not add new parameter-level semantics beyond the schema.

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 identifies the resource (Deribit BTC/ETH options) and the exact data points returned: open interest, strike walls, put/call balance, max pain, DVOL, and large trades. It uses a noun phrase ('The options picture') rather than a direct verb, but the scope and contents are unmistakable. It distinguishes itself from siblings by focusing on options-specific intelligence rather than general market data, though it does not name an alternative.

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 descriptionmakes the use case clear by enumerating options-relevant fields and saying it is aggregate market structure, so an agent can infer to use it for options sentiment/positioning questions. However, it does not explicitly state when to prefer it over siblings like market_snapshot or market_overview, nor mention exclusions or conditions.

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?