Skip to main content
Glama

skycloak_delete_webhook_subscription

Destructive

Delete a webhook subscription by specifying its ID and setting confirm=true to require explicit confirmation before removal.

Instructions

Delete a webhook subscription. Set confirm=true to proceed.

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_id": "<webhook_id>",
      "confirm": "<confirm>"
    },
    "name": "skycloak_delete_webhook_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesmust be true to confirm deletion
webhook_idYesthe webhook subscription ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=false, so the safety profile is carried by structured data. The description's only added content, the confirm gate, duplicates the confirm parameter's own schema description, and it never states that the deletion is permanent or what it invalidates.

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?

Two short sentences with zero filler, and the destructive action plus its precondition are front-loaded. Nothing could be removed without losing content.

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?

An output schema and full annotation coverage mean return values and safety are already handled, and the tool has only two parameters. Still, for a destructive operation the description omits consequence information an agent would want, such as whether the deletion is irreversible or stops future webhook deliveries.

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 both parameters (webhook_id, confirm) are documented in the schema itself. The description repeats the confirm requirement without adding format, ID provenance, or behavioral detail, 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?

States a specific verb and resource ("Delete a webhook subscription"), which is unambiguous and distinguishable from create/get/update siblings by the verb alone. It does not explicitly name or contrast with any alternative, so it stops short of a 5.

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 is the procedural gate "Set confirm=true to proceed," which is not when-to-use guidance. It says nothing about when deletion is appropriate versus updating/disabling a subscription, nor about prerequisites such as ownership or permissions.

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

Deploy Server

Other Tools