ChainHelix for Machines

chain_brief

Read-only

One chain, the whole read in one answer: market state with momentum, price walls, large transfers, bot activity, open interest, stablecoin flows and, for bitcoin, the mempool. Sections that fail are named in unavailable. Price: 5 cents per call.

Input Schema

Name	Required	Description	Default
`chain`	Yes	Chain name, one of bitcoin, ethereum, bnb, solana, avalanche, xrp, tron, polygon, sui. Example: bitcoin

Output Schema

Name	Required	Description
`chain`	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.
`generated`	Yes
`unavailable`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026

addedInput schema / properties / chain / description

Added value: +"Chain name, one of bitcoin, ethereum, bnb, solana, avalanche, xrp, tron, polygon, sui. Example: bitcoin"

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"

Changed2 schema fields changedSep 19, 2026

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: +{
+  "chain": "onchain.chain"
+}

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"
+}

AddedAug 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

readOnlyHint=true already covers the safety profile, and the description adds meaningful context beyond annotations: per-call cost (5 cents), the partial-failure contract (failed sections appear in an 'unavailable' field), and the bitcoin-only mempool caveat. It does not disclose latency or how the cost is metered/charged for failed sections, which would have pushed this higher.

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?

A single dense sentence that front-loads the value proposition ("the whole read in one answer") before the section list, followed by a short failure-mode clause and the price. The enumeration is long but each item distinguishes the tool's payload, so it earns its space; a minor trim would improve scanability.

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?

With annotations covering read-only safety, an output schema covering return shape, a fully documented single parameter, and description coverage of contents, cost, and partial-failure behavior, an agent has everything needed to decide to call this and interpret the result.

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% with a single enum-constrained parameter, so the schema already fully specifies the chain argument. The description adds no syntax or naming guidance beyond the schema beyond mentioning the bitcoin mempool special case, so the baseline of 3 applies.

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 verb and resource - a single call returning the complete read for one chain - and enumerates every section it aggregates (market state/momentum, price walls, large transfers, bot activity, open interest, stablecoin flows, bitcoin mempool). That enumeration makes it unmistakable against siblings like wall_map, whale_flows, mev_bots, open_interest and btc_mempool_history, which each return only one of these sections.

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?

"One chain, the whole read in one answer" clearly establishes the aggregation use case, implying this is the overview tool rather than the specialized single-section siblings. It does not explicitly name those alternatives or state when not to use it (e.g. when only one metric is needed), so it stops short of full routing guidance.

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?