Skip to main content
Glama

MaxRechnung

Test-Zustellung senden

send_webhook_test

Tarif: ab Business (darunter antwortet die API mit plan_required).

Test-Zustellung senden

Schickt sofort (nicht über die Queue) einen signierten POST mit type:"webhook.test" und gültigem X-Webhook-Signature-Header an den Endpunkt — zum Verifizieren der Signaturprüfung. Rührt die last_delivery_*-Statistik nicht an. Antwort: { object:"webhook_test", endpoint_id, delivered, status | error } (immer 200, auch wenn der Endpunkt nicht erreichbar war). Scope webhooks:write.

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_webhook_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPfad-Parameter id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The description adds substantial detail beyond the annotations: synchronous delivery rather than queued, the required scope webhooks:write, and the plan gate with its error code. It discloses that the call does not update the last_delivery_* statistics and that the response is always HTTP 200 even when the endpoint is unreachable, but it does not explain whether the call is idempotent or whether repeated calls are rate limited.

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?

The important operational facts are packed into three tight sentences, with the side-effect behavior and the response contract front-loaded right after the action. The plan-tier note opens the text before the purpose is stated, which is a small ordering flaw, but no sentence is wasted.

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

Completeness5/5

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

For a single-parameter test-delivery tool with no output schema, the description covers the return shape, the HTTP semantics, the side effects on statistics, the required scope, and the plan gate. The annotations already cover the safety profile, and the return contract is spelled out in prose, so nothing an agent needs to call it correctly is missing.

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 coverage is 100% and the sole parameter is a documented UUID id, so the schema carries the load. The description only implies that this id is the endpoint to deliver to; it adds no format, constraint, or behavior detail beyond the schema. A baseline 3 is the right score here.

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

Purpose5/5

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

Names the specific action (a test delivery over POST), the transport (immediate, not via the queue), the payload type ("webhook.test"), and the signature header used. That is far more than a restatement of the tool name and lets an agent distinguish it from a real delivery or a signature-verification call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit purpose for when to call it ("zum Verifizieren der Signaturprüfung") and states the plan prerequisite with the exact failure code (plan_required) below Business tier. It stops short of naming sibling tools or exclusion cases, so it is clear context without full alternative routing.

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