Skip to main content
Glama

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 readOnly/openWorld annotations, the description discloses cost ($0.10 USDC per call via x402), a failure contract (HTTP 503 with no charge when upstream sources are unavailable for >50% of fields), that the source is live, and that a data_source field discloses provenance (fred_api/fred_csv/fred_mixed). That is meaningful operational context an agent cannot get from annotations. It loses a point for repeating the 503/no-charge clause twice with slightly different wording, which muddies whether it is one condition or two.

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 metric inventory is front-loaded and earns its place, and the pricing/503/provenance notes are useful. However, the 503-no-charge statement appears twice in near-identical form, and the trailing '| x402 SLA' pipe-separated fragment reads as appended boilerplate rather than structured prose. Roughly a fifth of the text is redundant.

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 listing the returned fields, and it also covers pricing, error behavior, and provenance — enough for an agent to call it correctly. The only real gap is the omitted-parameter default and the semantics of 'all'. For a one-parameter read-only benchmark endpoint, this is close to complete.

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?

There is a single optional parameter (asset: BTC/ETH/all) with 0% schema description coverage, so the description must carry the meaning. It mentions BTC and ETH, implicitly framing the asset selector, but never explains the 'all' value or what happens when the parameter is omitted despite required-parameters being zero. Meaning is partly conveyed but the default behavior is left to guesswork.

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 a specific resource (crypto options implied volatility benchmarks) and enumerates the exact metrics returned: BTC/ETH 7D/30D IV, put/call ratio, fear/greed signal, term structure shape, and VIX comparison. It also names the underlying sources (Deribit public API + FRED). It stops short of explicitly distinguishing itself from siblings such as get_crypto_correlation_benchmark, but the domain is specific enough that confusion is unlikely.

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" signals the intended audience but is not a when-to-use rule; it gives no condition, exclusion, or named alternative. The agent can infer this is the volatility-surface tool rather than a correlation or yield tool, but the definition never says so. Usage is implied rather than stated.

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