ChainHelix for Machines

options_skew

Bitcoin and Ether options volatility surface from Deribit by expiry horizon: short = expiries 0 to 7 days out, front = 8 to 30 days, mid = 31 to 90 days, long = over 90 days. At the money, put and call implied volatility, risk reversal, butterfly, open interest, as the newest hourly average against 24 hours earlier within the same moneyness band definition (bandVersion). Each hour is published about 90 minutes after it ends; asOf is the start of the hour. Price: 2 cents per call.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`horizon`	No
`currency`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	Yes
`dataGaps`	No	Present only when the window of the answer overlaps a recorded data gap. Figures inside each listed period are incomplete. periods are the recorded gaps (end null while still open); atCall is measured against the window of this call and is left out of meta.contentHash.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"New value: +"25cc80db6d8e9eac73d47a50f7ad6333a21f1972d008a8fed0159de8bfb4b519"

Changed2 schema fields changedOct 16, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"New value: +"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"

changedInput schema / x-lexicon / version

Previous value: -"0.1.0"New value: +"0.2.0"

Changed4 schema fields changedOct 15, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / dataGaps

Added value: +{
+  "additionalProperties": false,
+  "description": "Present only when the window of the answer overlaps a recorded data gap. Figures inside each listed period are incomplete. periods are the recorded gaps (end null while still open); atCall is measured against the window of this call and is left out of meta.contentHash.",
+  "properties": {
+    "gaps": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "atCall": {
+            "additionalProperties": false,
+            "properties": {
+              "note": {
+                "type": "string"
+              },
+              "periodsInWindow": {
+                "items": {
+                  "additionalProperties": false,
+                  "properties": {
+                    "end": {
+                      "type": "number"
+                    },
+                    "ongoing": {
+                      "type": "boolean"
+                    },
+                    "start": {
+                      "type": "number"
+                    }
+                  },
+                  "required": [
+                    "start",
+                    "end"
+                  ],
+                  "type": "object"
+                },
+                "type": "array"
+              },
+              "shareOfWindowPct": {
+                "type": "number"
+              },
+              "windowEnd": {
+                "type": "number"
+              },
+              "windowStart": {
+                "type": "number"
+              }
+            },
+            "required": [
+              "windowStart",
+              "windowEnd",
+              "periodsInWindow",
+              "shareOfWindowPct",
+              "note"
+            ],
+            "type": "object"
+          },
+          "chain": {
+            "type": "string"
+          },
+          "data": {
+            "type": "string"
+          },
+          "periods": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "end": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "ongoing": {
+                  "type": "boolean"
+                },
+                "start": {
+                  "type": "number"
+                }
+              },
+              "required": [
+                "start",
+                "end"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "records": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "lost": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "lostUnit": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "record": {
+                  "type": "string"
+                },
+                "source": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "source",
+                "record"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "section": {
+            "type": "string"
+          },
+          "window": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "section",
+          "chain",
+          "data",
+          "window",
+          "periods",
+          "records",
+          "atCall"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "statement": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "statement",
+    "gaps"
+  ],
+  "type": "object"
+}

removedOutput schema / properties / meta

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "contentHash": {
-      "type": "string"
-    },
-    "generated": {
-      "type": "number"
-    },
-    "priceUsd": {
-      "type": "number"
-    },
-    "validUntil": {
-      "type": "number"
-    }
-  },
-  "type": "object"
-}

removedOutput schema / properties / receipt

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "bytes": {
-      "type": "number"
-    },
-    "covers": {
-      "type": "string"
-    },
-    "issuedAt": {
-      "type": "number"
-    },
-    "lookup": {
-      "type": "string"
-    },
-    "network": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "nonce": {
-      "type": "string"
-    },
-    "seq": {
-      "type": "number"
-    },
-    "settleTx": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "sha256": {
-      "type": "string"
-    },
-    "tool": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}

Changed1 schema field changedSep 21, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"

Changed1 schema field changedSep 19, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"

Changed1 schema field changedSep 19, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"

Changed3 schema fields changedSep 19, 2026

addedInput schema / x-aliases

Added value: +{
+  "currency": [
+    "Currency"
+  ]
+}

addedInput schema / x-lexicon

Added value: +{
+  "bundleSha256": "c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4",
+  "name": "ChainHelix Agentic Lexicon",
+  "resolve": "lexicon_resolve",
+  "spec": "lexicon_spec",
+  "version": "0.1.0"
+}

addedInput schema / x-vocab

Added value: +{
+  "currency": "data.currency",
+  "horizon": "market.horizon"
+}

Changed1 schema field changedSep 8, 2026
- addedOutput schema / properties / results / items / properties / source
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

Changed2 schema fields changedSep 5, 2026

addedOutput schema / properties / meta

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "contentHash": {
+      "type": "string"
+    },
+    "generated": {
+      "type": "number"
+    },
+    "priceUsd": {
+      "type": "number"
+    },
+    "validUntil": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / receipt

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "bytes": {
+      "type": "number"
+    },
+    "covers": {
+      "type": "string"
+    },
+    "issuedAt": {
+      "type": "number"
+    },
+    "lookup": {
+      "type": "string"
+    },
+    "network": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "nonce": {
+      "type": "string"
+    },
+    "seq": {
+      "type": "number"
+    },
+    "settleTx": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sha256": {
+      "type": "string"
+    },
+    "tool": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 1, 2026
- addedOutput schema / properties / results / items / properties / bandVersion
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
AddedAug 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries full behavioral burden and does disclose meaningful traits: hourly cadence, ~90-minute publication lag, asOf semantics (start of hour), data source (Deribit), and a per-call price of 2 cents. Auth, rate-limit, and error behavior are absent, but the latency and cost disclosures are genuinely useful context the schema cannot provide.

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?

Single dense paragraph, front-loaded with purpose and horizon definitions, with each sentence carrying a distinct fact (measures, comparison window, latency, price). The only cost is the run-on field-list sentence describing the returned metrics, which slightly hurts readability.

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?

For a 2-parameter tool with an output schema, the description covers purpose, parameter meanings, latency, and cost, and (lacking annotations) assumes the behavioral burden. Only auth/payment mechanics and rate limits are missing, which are minor given the stated pay-per-call model.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the enums supply only bare labels, but the description defines every horizon bucket in days (short = 0–7, front = 8–30, mid = 31–90, long = >90) and maps currency to BTC/ETH. It also flags the same-bandVersion consistency constraint, fully compensating for the schema gap.

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?

Names the exact resource (Bitcoin and Ether options volatility surface from Deribit), its partitioning dimension (expiry horizon), and the returned measures (ATM, put/call IV, risk reversal, butterfly, open interest, 24h comparison). An agent can distinguish this from sibling tools such as iv_summary or open_interest without opening any schema.

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?

No explicit when-to-use/when-not statement and no alternative sibling is named for routing. Usage is only implied by the horizon definitions and the 24-hour comparison framing, so an agent must infer that this is the skew-comparison tool rather than, say, iv_summary.

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

All ChainHelix for Machines 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?