Skip to main content
Glama

intel

by io.chainhelix
OverviewDiscussionsAdmin

webhook_status

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

TableJSON Schema
NameRequiredDescriptionDefault
idNo
secretNo
tenantYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
foundYes
webhooksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"
  3. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"
  4. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"
  5. 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"
+}
  6. Changed1 schema field changed
    • addedInput schema / required
      Added value: +[
+  "tenant"
+]
  7. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that without secret only id, active, and expiry are shown, and with secret more fields appear. It explicitly states 'Never returns the secret,' which is a critical behavior. It does not mention side effects (implied read-only) or error cases, but covers the main conditional behavior.

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 concise, two sentences plus a final clause. It front-loads the main purpose, then explains conditional behavior. No wasted words. Every sentence adds value.

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 format is covered. The description explains the parameters, the conditional fields, and the secret handling. It does not mention error cases, rate limits, or pagination, but for a simple status query these are likely minor. Overall, it provides sufficient context for an agent to call it correctly.

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 0%, so the description must explain parameters. It does: 'tenant' is your identity (wallet or key id), 'id' narrows to one webhook, and 'secret' is the signing secret from registration. It adds meaning beyond the schema by explaining roles and optionality. No format details are given, but semantics are clear.

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 verb 'webhook_status' meaning to list or get status of registered webhooks for a tenant. It specifies the resource (webhooks) and scope (tenant identity, optionally one id). It distinguishes from siblings like webhook_register and webhook_unregister by focusing on querying status, not creation or deletion.

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 implies usage: to check webhook status after registration, and explains the difference with/without secret. However, it does not explicitly mention when not to use it or contrast with alternatives. There is no direct statement like 'Use this to view webhook status; use webhook_register to create.' The context is clear but not explicit.

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