Skip to main content
Glama

send_test_webhook

Send a sample event to the webhook now and return the delivery result. (confirm-gated: previews until confirm: true)

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": "send_test_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The confirm-gated preview behavior is the main behavioral disclosure, but it merely restates what the input schema already says for the `confirm` parameter. Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), yet the description says nothing about failure/timeout handling, whether a test delivery is recorded in delivery history, or rate limits — and the outbound webhook call sits in some tension with openWorldHint=false.

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?

Two short, front-loaded sentences with the action first and the confirmation caveat second; no filler. The parenthetical is slightly duplicative of the schema, which keeps it from being maximally efficient.

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?

For a two-parameter mutation with no output schema, the definition should say more about what 'delivery result' contains and what happens to the webhook's delivery log. The confirm semantics are covered, but the undocumented `id` and unspecified return payload leave real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: `confirm` is fully documented in the schema, but `id` has no description and the tool text says only 'the webhook', never clarifying that `id` identifies the target webhook or what format it takes. The description does not compensate for the undocumented required parameter.

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 a concrete verb and resource ('Send a sample event to the webhook') plus the synchronous outcome ('return the delivery result'), which separates it from create_webhook or list_webhook_deliveries without naming them. It stops short of an explicit sibling distinction, so it lands at 4 rather than 5.

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?

The word 'sample' plus 'now' implies this is for validating an existing webhook configuration rather than creating or inspecting deliveries, but there is no explicit statement of when to use it instead of list_webhook_deliveries or set_webhook_active, and no preconditions (e.g., webhook must exist and be active) are given. Usage is inferable but not taught.

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.