Skip to main content
Glama

Register webhook

register_webhook

HMAC-signed POSTs for delivery.* events. Returns the signing secret once.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "register_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
eventsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already flag openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the bar is lower, yet the description adds genuinely new context: payloads are HMAC-signed, they fire for delivery.* events, and the signing secret is returned only once (so it must be persisted immediately). It stops short of stating auth requirements or what happens when the same URL is registered twice, which matters given non-idempotency.

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?

Two dense sentences with no filler, and the one-time secret disclosure is placed as its own sentence for emphasis. It is arguably over-terse for the amount of unstated wiring, but every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does cover the key return behavior (signing secret, returned once). However, for a non-idempotent, open-world registration call with 0% schema coverage, it omits auth/prerequisite information, duplicate-registration behavior, and any hint at the response object beyond the secret.

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 description coverage is 0%, so the description must compensate for two undocumented parameters. It partially does so by naming the 'delivery.*' event namespace, which explains the expected shape of `events`, but says nothing about `url` (format, reachability, HTTPS requirement) or whether `events` defaults to all events when omitted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys what the webhook does (HMAC-signed POSTs on delivery.* events) but never states that it creates/registers a subscription for the supplied URL — the verb is left to the title and name. An agent can infer registration from 'Returns the signing secret once', but the resource action itself is only implied, and no sibling (delete_webhook) is distinguished.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no pointer to alternatives such as delete_webhook for removing a subscription. The only usage-adjacent signal is the implicit warning that the secret appears once, which the agent must read between the lines to act on.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.