Skip to main content

ChainHelix for Machines

by io.chainhelix.mcp

Overview Discussions Admin

attest_status

Check one sealed claim by tenant plus seq or hash. Before reveal time only the receipt shows; after it the claim text and salt are included. With a nonce it returns the receipt of a paid answer instead: the sha256 of the answer bytes, its sequence number and, once sealed, the opBNB batch transaction and Merkle path

Input Schema

TableJSON Schema

Name	Required	Description	Default
`seq`	No
`hash`	No
`nonce`	No
`tenant`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`found`	Yes
`commit`	No
`record`	No
`receipt`	No

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"

Changed1 schema field changedOct 15, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

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: +{
+  "hash": "onchain.hashApi",
+  "nonce": "agent.nonce",
+  "seq": "agent.seq",
+  "tenant": "agent.tenant"
+}

Changed4 schema fields changedSep 5, 2026

addedInput schema / properties / nonce
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / commit

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "batch": {
+      "additionalProperties": false,
+      "properties": {
+        "committedAt": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "count": {
+          "type": "number"
+        },
+        "firstSeq": {
+          "type": "number"
+        },
+        "lastSeq": {
+          "type": "number"
+        },
+        "opbnbTx": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "root": {
+          "type": "string"
+        },
+        "sentAt": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "merklePath": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "h": {
+            "type": "string"
+          },
+          "pos": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "note": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    },
+    "verify": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / error
```
Added value: +{
+  "type": "string"
+}
```

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

First observedAug 17, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses the temporal reveal behavior (only the receipt before reveal time, claim text and salt after) and the conditional return contents for nonce mode (sha256 of answer bytes, sequence number, opBNB batch tx, Merkle path). It omits auth requirements, error conditions, and rate limits, but the temporal/conditional disclosure is substantive.

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?

Three sentences, front-loaded with the core purpose, then the two mode-specific behaviors. Dense and mostly waste-free, though the final sentence is a long run-on listing return fields.

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?

Given an output schema exists and no annotations are present, the description covers the important ground: identification inputs, the reveal-time conditional, and the nonce-mode return. It stops short of error handling and the interaction between the required tenant and the optional seq/hash/nonce parameters.

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 0%, so the description must compensate. It does clarify roles: tenant plus seq or hash identifies the claim, and nonce switches to the paid-answer receipt mode. It leaves gaps though, e.g., whether seq/hash are mutually exclusive or which is required when neither is supplied, and it gives no format hints for nonce or hash.

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 verb and resource ('Check one sealed claim by tenant plus seq or hash'), scoping to a single claim, which sets it apart from the plural siblings like list_attestations. The dual-mode behavior (receipt of paid answer when a nonce is supplied) slightly muddies the single-sentence purpose but is clearly described.

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?

Usage is implied through input conditions: seq/hash selects the sealed-claim mode, nonce selects the paid-answer receipt mode. However, it never states when to prefer this tool over attest, list_attestations, or verify_reveal, and gives no prerequisites or exclusions.

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

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?