Skip to main content
Glama

MaxRechnung

Webhook-Endpunkt löschen

delete_webhook
Destructive

Tarif: in jedem Tarif (Free, Pro, Business).

Webhook-Endpunkt löschen

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": {
      "id": "<id>"
    },
    "name": "delete_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPfad-Parameter id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds only plan availability and never states what deletion destroys (endpoint config, delivery history, active subscriptions), whether it is reversible, or whether confirmation is required.

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

Conciseness3/5

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

It is short and contains no filler prose, but the two lines are a metadata tag and a name restatement rather than a front-loaded explanation of behavior. Nothing is wasted, but little is delivered.

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

Completeness2/5

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

For an irreversible destructive operation with no output schema and no annotation detail about consequences, the description should explain impact and confirmability. Plan availability alone does not prepare an agent to invoke a delete safely.

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% for the single id parameter, and the description adds no meaning beyond it (e.g., which webhook ID namespace, whether it must exist). Baseline 3 applies when the schema does all the work.

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

Purpose2/5

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

"Webhook-Endpunkt löschen" simply restates the tool name and title in German; there is no additional qualifier about scope, meaning, or which webhook resources are affected. An agent learns nothing beyond what the identifier delete_webhook already implies.

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?

The only guidance offered is a plan-availability note ("in jedem Tarif (Free, Pro, Business)"), which is a precondition, not when-to-use guidance. Nothing distinguishes this from siblings such as get_webhook, create_webhook, or send_webhook_test, and no exclusions or cautions are given.

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