Skip to main content
Glama

Test webhook

test_webhook

Send a test request to a webhook URL. Paid plans only.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true and destructiveHint=false, so the external-call nature is partially covered; the description's real contribution is the paid-plan gate. It does not disclose what the test payload is, what the response indicates, or whether the call counts against quotas or rate limits.

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 sentences with no waste, and the action is front-loaded before the plan restriction. Nothing superfluous, though the second sentence is a bare fragment that could be folded in.

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?

A diagnostic tool with no output schema should explain what a 'test request' delivers and what a success or failure looks like, and it does neither. Combined with the unresolved id-vs-URL question, an agent lacks what it needs to call this confidently.

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

Parameters1/5

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

Schema coverage is 0% and the single required parameter is an undescribed 'id', so the description must compensate — instead it says 'webhook URL', which points to a different value shape and actively misleads about what to pass. The gap is made worse rather than filled.

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 ('Send a test request to a webhook URL'), which is clearly distinct from the add/delete/list webhook siblings. The only friction is that the schema takes an 'id' while the description speaks of a 'URL', leaving the target ambiguous.

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?

Includes one useful prerequisite ('Paid plans only') but never says when to prefer this over alternatives such as list_webhooks or set_webhook_enabled, nor when not to call it. Usage is implied by the name rather than explained.

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