Skip to main content
Glama

Options volatility

options_volatility
Read-only

Option-implied volatility for BTC, ETH or SOL from Deribit's public market data: ATM implied volatility by expiry (the term structure, interpolated at each expiry's forward), 25-delta call and put IV with the risk reversal (skew) and butterfly, put/call open-interest and volume ratios per expiry and in total, the index price, and Deribit's DVOL 30-day volatility index with its 24h range (BTC and ETH; Deribit publishes none for SOL). Deltas are Black-76 forward deltas from Deribit mark IVs. Fails (and is not charged) if Deribit's option data is unavailable. Costs $0.005 USDC per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "options_volatility"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyNoUnderlying: BTC, ETH, SOL (default BTC)
maxExpiriesNoExpiries to return, nearest first, 1–30 (default 12)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses the upstream dependency (Deribit), the billing model ($0.005 USDC per call), that failures are not charged, and the delta methodology (Black-76 forward deltas from mark IVs). The note that SOL has no DVOL is exactly the kind of partial-data disclosure an agent needs.

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 the core verb+resource, then the output inventory, then methodology, then cost/failure — a sensible priority order. The middle clause is a long comma-separated run-on that is dense but every item listed is substantive return-value information, not 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?

There is no output schema, and the description compensates by enumerating the returned fields, units, and the SOL DVOL gap. Combined with the failure and pricing semantics, an agent has everything needed to decide, call, and interpret results.

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 both parameters (currency, maxExpiries) are already documented with defaults and ranges. The description restates the asset universe but adds no syntax or behavioral detail beyond the schema — 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?

States a specific resource (option-implied volatility) with a named source (Deribit public market data) and a bounded asset universe (BTC, ETH, SOL). It enumerates the concrete outputs — ATM IV term structure, 25-delta call/put IV, risk reversal, butterfly, OI/volume ratios, index price, DVOL — which no sibling tool covers.

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 scope is clear enough to select correctly: it is the options-volatility surface tool, Deribit-only, with a stated per-call price and a stated failure mode, so an agent can weigh cost and source before calling. It stops short of naming alternatives (e.g., open_interest_change or perp_market_overview for non-options data) or stating exclusions explicitly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources