Skip to main content
Glama

Set notification webhook

set_notification_webhook
DestructiveIdempotent

Signed account webhook (returns secret). Events: domain.registered, domain.registration_pending, domain.registration_completed, domain.transfer_started, domain.transfer_completed, domain.renewed, domain.expiring, dns.changed. Verify X-StableDomains-Signature = sha256 HMAC of the raw body with the secret; retries for 24h, dedupe on X-StableDomains-Delivery. null to remove.

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": {
      "webhook_url": "<webhook_url>"
    },
    "name": "set_notification_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhook_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already flag idempotentHint=true and destructiveHint=true, and the description goes well beyond them by explaining the signature scheme (sha256 HMAC of the raw body, X-StableDomains-Signature), the 24h retry window, the dedupe header, and that the call returns a secret. These are exactly the operational details an agent needs to configure a consumer correctly and are not derivable from the structured fields.

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?

A single dense passage with no filler: the core purpose and return value come first, followed by the event vocabulary and verification contract, ending with the removal semantics. The event list is long but functional — it is the contract the caller must implement — so every clause earns its place.

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 one-parameter configuration tool with no output schema, the description covers the signing/verification contract, retry and dedupe behavior, event set, and removal path. The remaining gap is whether a set call replaces any existing webhook and whether account-level permissions are required, which matters given destructiveHint=true.

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 0%, so the schema supplies only 'string | null' with no meaning. The description partially compensates by defining the null case as removal and by implying the value is a signed endpoint URL, but it never states URL requirements (https, reachability) or what happens to an existing webhook on overwrite.

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 identifies the resource precisely ('Signed account webhook') and discloses a key outcome ('returns secret'), plus 'null to remove' clarifies the full set/replace/remove lifecycle. It does not explicitly restate the verb 'set', relying on the tool name, but the resource and effect are unambiguous enough that an agent knows exactly what this configures.

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 rather than stated: the enumerated event list tells the agent this is the endpoint for domain/DNS notifications, and 'null to remove' tells it how to unsubscribe. There is no explicit when-to-use-vs-alternatives guidance, though no sibling tool covers webhook configuration, so the risk of mis-selection is low.

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.

Resources