ChainHelix for Machines

webhook_register

Destructive

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

Name	Required	Description	Default
`url`	Yes	https URL on a public host name, up to 500 characters; localhost, .local, .internal and .lan names, private IPv4 addresses and IPv6 literals are refused. Example: https://example.com/hooks/chainhelix
`events`	No	Event names, any of signal_sealed, trade_closed, lead_alert; absent = signal_sealed and trade_closed. Example: ["signal_sealed", "lead_alert"]

Output Schema

Name	Required	Description	Default
`id`	No
`url`	No
`note`	No
`error`	No
`events`	No
`secret`	No
`daysAdded`	No
`expiresAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 25, 2026

addedInput schema / properties / events / description

Added value: +"Event names, any of signal_sealed, trade_closed, lead_alert; absent = signal_sealed and trade_closed. Example: [\"signal_sealed\", \"lead_alert\"]"

addedInput schema / properties / url / description

Added value: +"https URL on a public host name, up to 500 characters; localhost, .local, .internal and .lan names, private IPv4 addresses and IPv6 literals are refused. Example: https://example.com/hooks/chainhelix"

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"

Changed2 schema fields changedOct 15, 2026

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

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"

Changed3 schema fields changedSep 19, 2026

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

Changed1 schema field changedSep 17, 2026

changedInput schema / properties / events / items / enum

Previous value: -[
-  "signal_sealed",
-  "trade_closed"
-]New value: +[
+  "signal_sealed",
+  "trade_closed",
+  "lead_alert"
+]

Changed1 schema field changedSep 16, 2026

changedInput schema / properties / events / items / enum

Previous value: -[
-  "signal_sealed",
-  "trade_closed",
-  "mev_flow"
-]New value: +[
+  "signal_sealed",
+  "trade_closed"
+]

Changed1 schema field changedSep 16, 2026

changedInput schema / properties / events / items / enum

Previous value: -[
-  "signal_sealed",
-  "trade_closed"
-]New value: +[
+  "signal_sealed",
+  "trade_closed",
+  "mev_flow"
+]

Changed1 schema field changedSep 5, 2026

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

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing cost (70 cents per call / 7 days), that the API key does NOT cover this tool (a distinct payment/auth path agents must know about), that deliveries are cryptographically signed, and that re-registering with the same URL extends rather than replaces. These are exactly the operational facts an agent needs before calling a paid, destructiveHint=true endpoint.

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?

Front-loaded with the core purpose and largely waste-free, but the parenthetical asides ('the sealed signal stream the moment each signal exists', the triple price repetition) make it denser than it needs to be. The pricing fact is stated twice in different words.

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?

Output schema exists, so no return-value explanation is needed, and the description still covers payment model, auth separation from the API key, delivery signing, idempotent-extension behavior, and the sibling boundary. Nothing an agent needs in order to register 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%, so the schema already documents the https-only URL constraint, the 500-character limit, the refused hostnames, and the event enum with its default. The description adds only that lead_alert is 'opt in by name', which is marginal; baseline 3 is appropriate when the schema carries the semantics.

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?

The description opens with a concrete verb+resource+mode: 'ChainHelix events PUSHED to your https URL instead of polling', and enumerates the exact event types delivered. It explicitly carves out the MEV minute stream as belonging to the sibling stream_register, so an agent can distinguish it 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?

It gives a clear selection rule (push instead of polling) and names the alternative registration (stream_register) for the MEV flow, plus the extension pattern 'call again with the same URL any time to extend'. Explicit when-not-to-use guidance beyond the MEV carve-out is absent, keeping it just short of a 5.

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?