Crypto Bot Audit + Market Data (x402 paid)

Deribit daily volatility index

market_deribit_volatility_index

Read-onlyIdempotent

Historical daily candles of Deribit's DVOL-style volatility index for an underlying — the implied-vol level options are priced off, as OHLC per day. Costs $0.001 USDC per call. Byte-identical to GET /market/deribit-volatility-index?currency=BTC&days=20.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No	days of history (max 365) (default 30)
`currency`	No	underlying whose volatility index Deribit publishes (default "BTC")

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ts`	No
`days`	No
`note`	No
`rows`	No
`count`	No
`found`	No
`stale`	No
`caveat`	No
`reason`	No
`source`	No
`currency`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "caveat": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "count": {
+      "type": "integer"
+    },
+    "currency": {
+      "type": "string"
+    },
+    "days": {
+      "type": "integer"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "rows": {
+      "items": {},
+      "type": "array"
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "ts": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile. The description adds genuinely useful behavioral context beyond that: a per-call cost of $0.001 USDC and byte-identical equivalence to a specific REST endpoint. No contradiction with 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?

Two tight sentences with no filler: the first fronts the resource and data format, the second adds cost and API equivalence. Every clause earns its place.

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?

For a simple two-optional-param, read-only tool with a full output schema and documented annotations, the description is complete. It covers purpose, data shape, cost, and endpoint equivalence; nothing essential is missing.

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?

Param schema coverage is 100%, and both params are already well documented with defaults and constraints. The description adds little beyond restating 'underlying' and showing the currency/days example in the endpoint URL, so it does not materially expand on the schema.

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 states a specific resource ('Deribit's DVOL-style volatility index') and the exact data shape ('Historical daily candles ... as OHLC per day'). It distinguishes itself from siblings like market_deribit_index by emphasizing historical candle data rather than a current spot/level reading.

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 makes the intended use clear for anyone seeking historical daily OHLC volatility-index data, but it does not explicitly say when to choose this tool over alternatives like market_deribit_index or market_deribit_funding_window. No exclusions, prerequisites, or alternative-routing guidance is provided.

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

All Crypto Bot Audit + Market Data (x402 paid) 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?