Skip to main content
Glama

intel

by io.chainhelix
OverviewDiscussionsAdmin

webhook_register

70 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. A ChainHelix API key does not cover this tool. Get 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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
eventsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
urlNo
noteNo
errorNo
eventsNo
secretNo
receiptNo
daysAddedNo
expiresAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"
  2. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"
  3. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"
  4. 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"
+}
  5. Changed1 schema field changed
    • changedInput schema / properties / events / items / enum
      Previous value: -[
-  "signal_sealed",
-  "trade_closed"
-]New value: +[
+  "signal_sealed",
+  "trade_closed",
+  "lead_alert"
+]
  6. Changed1 schema field changed
    • changedInput schema / properties / events / items / enum
      Previous value: -[
-  "signal_sealed",
-  "trade_closed",
-  "mev_flow"
-]New value: +[
+  "signal_sealed",
+  "trade_closed"
+]
  7. Changed1 schema field changed
    • changedInput schema / properties / events / items / enum
      Previous value: -[
-  "signal_sealed",
-  "trade_closed"
-]New value: +[
+  "signal_sealed",
+  "trade_closed",
+  "mev_flow"
+]
  8. 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"
+}
  9. Added

TDQS

A4.5/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses cost, payment rails, lack of API-key coverage, 7-day validity, renewal behavior, signed deliveries, and the specific events delivered. This is substantially more transparent than typical tool descriptions.

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?

Every sentence adds relevant information and the description is well-packed. However, it leads with pricing and payment details before stating the tool's primary purpose, and the long event-list sentence is dense. A more front-loaded structure would make the main action immediately clear.

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?

For a paid webhook registration tool with an output schema, the description covers purpose, cost, auth, event semantics, renewal, and signing. It does not clarify what happens when calling with an existing URL or how omitted events are handled, but the output schema likely covers the registration response. Overall it is complete enough for correct invocation.

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%, but the description compensates by explaining the event options (signal_sealed, trade_closed, lead_alert) with meaning, and identifies url as an https endpoint. It does not specify URL format beyond https or describe default behavior if events is omitted, but the essential semantics are present.

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 clearly states the core action: 'Get ChainHelix events PUSHED to your https URL instead of polling.' It names the specific event types and explicitly distinguishes the tool from the separate stream_register for MEV flow, so an agent can identify it among many siblings.

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?

The description provides strong usage context by contrasting webhooks with polling and naming stream_register as the alternative for MEV flow. It also states the payment prerequisite. However, it does not mention the closely related lifecycle siblings webhook_status or webhook_unregister, so guidance on when to use those is missing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All intel 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