Skip to main content
Glama

MaxRechnung

Webhook-Endpunkt registrieren

create_webhook

Tarif: ab Business (darunter antwortet die API mit plan_required).

Webhook-Endpunkt registrieren

Antwortet einmalig mit secret (whsec_…) zum Verifizieren der Signatur. Scope webhooks:write.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoJSON-Request-Body.
_idempotency_keyNoOptional. Geht als Header `Idempotency-Key` an die API: derselbe Wert mit demselben Aufruf liefert 24 Stunden lang die erste Antwort zurück, statt den Vorgang zu wiederholen. Bei einem Wiederholversuch denselben Wert schicken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare that this is a non-read-only, non-destructive write. The description adds material behavior beyond that: a plan-tier gate with the concrete error code `plan_required`, the required `webhooks:write` scope, and the crucial fact that the `secret` is returned only once. Rate limits and the per-account endpoint cap are left to the schema.

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?

Four short lines, each carrying a distinct fact: plan gate with error code, action, one-time secret, required scope. Nothing is padded, though the action line duplicates the title.

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 two-parameter creation tool with no output schema, the description covers the essentials an agent needs: permission scope, plan requirement with failure signal, and the fact that the returned secret is not retrievable later. Missing only minor details such as behavior when the endpoint limit is already reached.

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 100%, and the schema itself documents the HTTPS URL constraint, the default of all events, and the per-account/per-event endpoint limits. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 states the specific action (registering a webhook endpoint) and adds the distinctive outcome of the call (a one-time `secret` in `whsec_…` format for signature verification). It does not explicitly distinguish itself from siblings such as `send_webhook_test` or `verify_webhook_signature`, and the second line merely repeats the title.

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?

Preconditions are given clearly: a Business plan or higher is required, otherwise the API returns `plan_required`, and the `webhooks:write` scope is needed. However, there is no explicit when-to-use versus when-not-to-use guidance and no named alternative for other webhook-related operations.

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