Skip to main content
Glama

skycloak_test_webhook_subscription

Sends a test event to a specified webhook subscription so you can verify delivery and event handling before relying on it in production.

Instructions

Send a test event to a webhook subscription.

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>"
    },
    "name": "skycloak_test_webhook_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_typeNooptional event type to test
webhook_idYesthe webhook subscription ID

Output Schema

NameRequiredDescriptionDefault
successYes
delivery_idYes
duration_msYes
attempted_atYes
error_messageNo
response_bodyNo
response_codeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond restating the action: it does not say that a real HTTP request is delivered to the customer's endpoint, whether the test event counts toward delivery stats or failure counters, or what happens on endpoint failure. For an open-world, non-idempotent tool, that is a meaningful gap.

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?

A single front-loaded sentence with zero filler or repetition. It is economical, though the extreme brevity is a symptom of under-specification rather than disciplined conciseness.

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 exists and all parameters are documented, so the agent knows the mechanical shape of the call. What is missing is behavioral context proportional to an open-world, side-effecting tool: whether the test event is actually delivered externally, how failures surface, and whether repeated calls cause repeated 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%, so both webhook_id and event_type are already documented in the schema. The description adds no extra meaning about event_type (defaults, allowed values, or how to discover them via the list_webhook_event_types sibling). Baseline 3 applies when the schema does the heavy lifting.

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 gives a specific verb ('Send a test event') and resource ('a webhook subscription'), which is enough to distinguish it from CRUD siblings like create/delete/update_webhook_subscription. It stops short of differentiating itself from the other 'test_*' siblings such as test_smtp or test_siem_destination, but the webhook resource anchor is clear.

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 mention of prerequisites (does the subscription need to be enabled or active?), and no note about when to omit event_type versus supply it. The agent must infer entirely from the schema.

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