Skip to main content
Glama
Sign In

ChainHelix for Machines

by io.chainhelix.mcp
OverviewDiscussionsAdmin

attest_status

Read-only

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

NameRequiredDescriptionDefault
seqNoSequence number of the claim in the tenant stream, whole number from 1. Example: 3
hashNosha256 of the sealed claim, 64 hex characters. Example: 9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08
nonceNoPayment nonce of a paid answer, the nonce field of its receipt (x402: 0x and 64 hex characters). Example: 0x7d3c8a2f5e9b1d4c6a0f8e2b3c5d7a9f1e4b6c8d0a2f4e6b8c1d3e5f7a9b0c2d
tenantYesTenant identity: the paying wallet address in lower case, or the numeric key id of a ChainHelix subscription. Example: 0x000000000000000000000000000000000000dead

Output Schema

NameRequiredDescriptionDefault
errorNo
foundYes
commitNo
recordNo
receiptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / hash / description
      Added value: +"sha256 of the sealed claim, 64 hex characters. Example: 9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08"
    • addedInput schema / properties / nonce / description
      Added value: +"Payment nonce of a paid answer, the nonce field of its receipt (x402: 0x and 64 hex characters). Example: 0x7d3c8a2f5e9b1d4c6a0f8e2b3c5d7a9f1e4b6c8d0a2f4e6b8c1d3e5f7a9b0c2d"
    • addedInput schema / properties / seq / description
      Added value: +"Sequence number of the claim in the tenant stream, whole number from 1. Example: 3"
    • addedInput schema / properties / tenant / description
      Added value: +"Tenant identity: the paying wallet address in lower case, or the numeric key id of a ChainHelix subscription. Example: 0x000000000000000000000000000000000000dead"
  2. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"New value: +"25cc80db6d8e9eac73d47a50f7ad6333a21f1972d008a8fed0159de8bfb4b519"
  3. Changed2 schema fields changed
    • 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"
  4. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  5. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"
  6. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"
  7. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"
  8. Changed2 schema fields changed
    • 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"
+}
  9. Changed4 schema fields changed
    • 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"
+}
  10. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds genuinely non-obvious behavior: output is time-gated on reveal (receipt only before, claim text plus salt after), and nonce-keyed calls return a different payload including opBNB batch tx and Merkle path once sealed. That is useful behavioral context beyond the structured fields.

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 dense sentences, front-loaded with the core 'check one sealed claim' purpose and followed by the reveal-time and nonce variants. No filler, though the heavy domain jargon ('sealed', 'receipt', 'salt') slightly slows parsing.

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?

An output schema exists, so return shapes needn't be spelled out and the description still covers both call modes and the reveal-time visibility rule. Missing: the seq-vs-hash selection rule and error behavior (e.g., unknown seq/hash), which matter for a 4-parameter lookup.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds semantics the schema cannot express: nonce is not just another filter but a mode switch to paid-answer receipt lookup. It still doesn't state what happens if both seq and hash are supplied or neither is, despite tenant being the only required field.

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 (Check) and resource (one sealed claim) and clearly partitions the tool into two modes: lookup by tenant+seq/hash vs. a receipt lookup keyed by nonce. It doesn't name any sibling (attest, list_attestations, verify_reveal) so an agent still has to infer which of those this replaces, keeping it short of a 5.

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 explains the condition that switches behavior ('with a nonce it returns...', 'before reveal time... after it...'), which is real usage guidance for parameter-driven mode selection. However it never says when to prefer this over attest/verify_reveal/list_attestations, so sibling routing is left to inference.

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 toolsInspect
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