Skip to main content
Glama

Stratalize Intelligence

Get Options Iv Benchmark

get_options_iv_benchmark
Read-only

Crypto options implied volatility benchmarks — BTC and ETH 7D/30D IV, put/call ratio, fear/greed signal, term structure shape, and VIX comparison. Source: Deribit public API + FRED. For options traders and volatility agents. Live source. Returns HTTP 503 (no charge) if upstream source unavailable for >50% of fields. | x402 SLA: $0.10 USDC per call. Returns HTTP 503 (no charge) when upstream data sources unavailable. data_source field discloses provenance (fred_api/fred_csv/fred_mixed).

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": "get_options_iv_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnly/openWorld/non-destructive), the description contributes real operational facts: live source, an explicit failure mode (HTTP 503 with no charge when upstream is unavailable for >50% of fields), per-call pricing ($0.10 USDC via x402), and the data_source provenance field values. It loses a point only because the 503 behavior is stated twice and no rate-limit or latency expectation is given.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The core content is front-loaded and information-dense, but the 503/no-charge sentence appears twice in near-identical wording, and the trailing pricing/SLA sentence duplicates the failure-mode statement again. Trimming the repetition would make it noticeably tighter.

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?

With no output schema, the description does the work of telling the agent what comes back (the field list), where it comes from, and how failures are signaled, which is solid for a one-parameter read tool. The only remaining gap is the default/behavior of the asset parameter when omitted.

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 0%, so the description must carry the parameter meaning. It mentions BTC and ETH, which map to two of the three enum values, but it never explains the "all" option, whether "all" is the default, or how results differ between a single asset and "all".

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 names the exact resource and enumerates its contents: BTC/ETH 7D/30D implied volatility, put/call ratio, fear/greed signal, term structure shape, and VIX comparison, plus the upstream sources (Deribit + FRED). It is unmistakably distinct from the other benchmark siblings by content, though it never explicitly frames itself as the options-IV alternative to any named tool.

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?

"For options traders and volatility agents" implies the audience and therefore the usage context, but there is no explicit when-to-use, when-not-to-use, or comparison to any sibling benchmark. An agent must infer that this is the crypto-volatility option rather than a generic crypto or correlation tool.

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