Skip to main content
Glama

ChainHelix for Machines

by io.chainhelix.mcp
OverviewDiscussionsAdmin

webhook_register

ChainHelix events PUSHED to your https URL instead of polling: signal_sealed (the sealed signal stream the moment each signal exists), trade_closed (every finished trade with its result), lead_alert (each lead alert the moment it is written, opt in by name). The MEV flow minute stream is a separate registration, stream_register. 70 cents buys 7 days of delivery; call again with the same URL any time to extend. Deliveries are signed so you can verify each one came from us. Price: 70 cents per call. A ChainHelix API key does not cover this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
eventsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
urlNo
noteNo
errorNo
eventsNo
secretNo
daysAddedNo
expiresAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"New value: +"25cc80db6d8e9eac73d47a50f7ad6333a21f1972d008a8fed0159de8bfb4b519"
  2. 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"
  3. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • 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"
-}
  4. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"
  5. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"
  6. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"
  7. Changed3 schema fields changed
    • addedInput schema / x-aliases
      Added value: +{
+  "events": [
+    "Events"
+  ],
+  "url": [
+    "Url",
+    "URL"
+  ]
+}
    • 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: +{
+  "events": "common.events",
+  "url": "data.url"
+}
  8. Changed1 schema field changed
    • changedInput schema / properties / events / items / enum
      Previous value: -[
-  "signal_sealed",
-  "trade_closed"
-]New value: +[
+  "signal_sealed",
+  "trade_closed",
+  "lead_alert"
+]
  9. Changed1 schema field changed
    • changedInput schema / properties / events / items / enum
      Previous value: -[
-  "signal_sealed",
-  "trade_closed",
-  "mev_flow"
-]New value: +[
+  "signal_sealed",
+  "trade_closed"
+]
  10. Changed1 schema field changed
    • changedInput schema / properties / events / items / enum
      Previous value: -[
-  "signal_sealed",
-  "trade_closed"
-]New value: +[
+  "signal_sealed",
+  "trade_closed",
+  "mev_flow"
+]
  11. Changed1 schema field changed
    • 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"
+}
  12. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses cost (70 cents per call), delivery duration (7 days), the extend-by-recalling behavior, that deliveries are signed for verification, and that a ChainHelix API key does not cover this tool. It omits failure/retry semantics and any constraints on URL validity beyond 'https'.

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?

Dense and front-loaded, with event types and the sibling comparison stated early. It slightly repeats the pricing ('70 cents buys 7 days' then 'Price: 70 cents per call'), which is minor waste in an otherwise efficient description.

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?

The price, delivery window, signing, extension behavior, auth exclusion, and event catalog cover what an agent needs to call this correctly, and an output schema exists so return values need not be explained. Remaining gaps (retry/failure handling) are secondary for a registration tool.

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 description coverage is 0%, so the description must compensate, and it does for events: each of signal_sealed, trade_closed, and lead_alert is explained, plus the 'opt in by name' note for lead_alert. For url it conveys HTTPS and the 'same URL extends' semantics, though it adds no format details.

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+resource (register events to be pushed to your URL) and enumerates the exact payload types delivered (signal_sealed, trade_closed, lead_alert). It explicitly distinguishes itself from the sibling stream_register for the MEV flow minute stream, so an agent can route without opening either schema.

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?

Frames the tool against the alternative of polling and names stream_register as the separate registration for the MEV flow stream, which is clear context. It also notes that re-calling with the same URL extends rather than duplicates, but it does not state any exclusions (e.g., when webhook delivery is inappropriate or what happens if the URL is unreachable).

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