Skip to main content
Glama
Sign In

ChainHelix for Machines

by io.chainhelix.mcp
OverviewDiscussionsAdmin

webhook_status

Read-only

Your registered webhooks for your tenant identity (your paying wallet, or your key id), optionally narrowed to one id. Without secret each webhook shows id, active and expiry only. With the signing secret from registration, that webhook also shows its url, events, chains and watches. Never returns the secret

Input Schema

NameRequiredDescriptionDefault
idNoWebhook id from registration, 8 hex characters. Example: 3f9a0c1b
secretNoSigning value from registration, 32 hex characters. Example: 00112233445566778899aabbccddeeff
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
webhooksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"Webhook id from registration, 8 hex characters. Example: 3f9a0c1b"
    • addedInput schema / properties / secret / description
      Added value: +"Signing value from registration, 32 hex characters. Example: 00112233445566778899aabbccddeeff"
    • 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. Changed4 schema fields changed
    • addedInput schema / properties / secret
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / x-aliases / secret
      Added value: +[
+  "Secret",
+  "secrets"
+]
    • addedInput schema / x-vocab / secret
      Added value: +"common.secret"
    • addedOutput schema / properties / webhooks / items / properties / detail
      Added value: +{
+  "type": "string"
+}
  6. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"
  7. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"
  8. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"
  9. Changed3 schema fields changed
    • addedInput schema / x-aliases
      Added value: +{
+  "id": [
+    "Id",
+    "ID",
+    "@id"
+  ]
+}
    • 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: +{
+  "id": "data.id",
+  "tenant": "agent.tenant"
+}
  10. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond readOnlyHint, the description discloses meaningful behavior: output fields depend on whether the signing secret is supplied, and the secret itself is never returned. This gives the agent clear expectations about access level and response visibility.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and then explains the secret-based visibility rules efficiently. Every sentence carries relevant information without repetition or bloat.

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?

Given the readOnly annotation and existing output schema, the description provides enough context about filtering, secret-based field visibility, and the secret non-disclosure guarantee. Nothing critical for correct invocation is missing.

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 100%, so the schema already documents the parameters. The description adds useful semantics by explaining how id narrows to one webhook and how secret changes which fields are returned, while tenant is covered by the schema.

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?

The description clearly names the resource (registered webhooks) and the optional narrowing to one id, so an agent can understand it retrieves webhook status. It lacks an explicit verb such as "list" or "get", which keeps it from a top score.

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: use it to view registered webhooks, with or without an id and signing secret. However, it does not explicitly say when to use this versus webhook_register or webhook_unregister, nor does it state exclusions or alternatives.

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