ChainHelix for Machines

wall_map

Read-only

Support and resistance price walls per chain with touch counts and strength, from hourly to weekly market structure, the same wall map the ChainHelix engine trades with: the five strongest levels on each side of price, and the nearest of them with its distance in percent. Omit chain for all nine. Price: 2 cents per call.

Input Schema

Name	Required	Description	Default
`chain`	No	Chain name, one of bitcoin, ethereum, bnb, solana, avalanche, xrp, tron, polygon, sui; absent = every chain. Example: bnb

Output 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 25, 2026

addedInput schema / properties / chain / description

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

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

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

addedOutput schema / properties / results / items / properties / asOf
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
addedOutput schema / properties / results / items / properties / source
```
Added value: +{
+  "type": "string"
+}
```

First observedAug 17, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond readOnlyHint=true, the description discloses the output shape (five strongest levels per side, nearest level with distance in percent), the timeframes covered, the all-chains default, and an explicit cost of 2 cents per call. That cost and result-shape disclosure is meaningful context annotations cannot carry; only the lack of latency/rate-limit detail keeps it from a 5.

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?

The resource and the result contract are front-loaded, and every clause (timeframes, five-per-side, nearest with distance, chain default, price) carries information. The middle sentence is a long colon-chained run-on that could be split, which is the only real structural flaw.

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 an output schema present the description needn't enumerate return fields, yet it still summarizes the result contract, and it covers the one optional parameter's default plus per-call cost. Nothing an agent needs to select or invoke this tool correctly 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?

Schema coverage is 100% and the chain parameter already documents the enum, the 'absent = every chain' default, and an example. The description's 'Omit chain for all nine' only confirms the count of chains, adding little beyond the schema — baseline 3.

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?

States a specific resource — support/resistance price walls with touch counts and strength — plus its granularity (hourly to weekly) and chain scoping. It never names a sibling tool to contrast against, so the agent must infer that prices/candles/market_state are different artifacts, but the resource itself is unmistakable.

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 only usage instruction is 'Omit chain for all nine,' which tells the agent how to broaden scope but not when to prefer this tool over prices, candles, or market_state. Usage is implied by the domain rather than stated.

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?