Skip to main content
Glama

MaxRechnung

Empfangene Signatur prüfen

verify_webhook_signature
Read-only

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

Empfangene Signatur prüfen

Prüft eine empfangene Zustellung: Request-Body = der exakte rohe Payload. Mit Header X-Webhook-Signature-V2 (t=<unix>,v1=<hex>) wird zeitgebunden geprüft (scheme: "v2", ?tolerance= Sekunden, Vorgabe 300; reason = malformed | expired | mismatch), sonst klassisch über X-Webhook-Signature (mit oder ohne sha256=-Präfix) oder ?signature= (scheme: "v1"). Vergleich konstantzeitig gegen das Secret des Endpunkts. Kein Seiteneffekt. Scope webhooks:read. So verifiziert man auch selbst: V2 HMAC_SHA256(t + "." + rawBody, secret) als Hex gegen v1, dazu t im Fenster; klassisch HMAC_SHA256(rawBody, secret) als Hex mit sha256=-Präfix.

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

Input Schema

NameRequiredDescriptionDefault
idYesPfad-Parameter id
bodyNoJSON-Request-Body.
signatureNoAlternative zum Header `X-Webhook-Signature`.
toleranceNoReplay-Fenster in Sekunden für `X-Webhook-Signature-V2` (Abstand von `t` zum Jetzt).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/destructiveHint annotations: it discloses the plan restriction, the scope, the constant-time comparison, the fact that there is no side effect, and the concrete failure reason values (malformed, expired, mismatch) that the caller must handle. This is unusually rich behavioral context for a read-only tool.

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?

Dense but mostly earns its length, with the header names and reason codes called out inline. Minor waste: the plan-tier line precedes the actual purpose, and the closing sentence explaining how to compute the HMAC yourself is implementation detail that a verifier caller rarely needs.

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?

With no output schema, the description must convey the return shape; it names the `reason` and `scheme` values but never states what a successful verification returns (e.g., a validity flag). Inputs and failure modes are well covered, so the gap is narrow but real.

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

Parameters4/5

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

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning: `body` must be the exact raw payload (the schema only says "JSON-Request-Body"), `signature` may carry or omit the sha256= prefix, and `tolerance` only applies to the V2 header path with a default of 300 seconds.

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 concrete verb+resource: it verifies a received webhook delivery against the endpoint's secret, and it is clearly distinct from create_webhook/send_webhook_test siblings. It does not explicitly name an alternative tool, but the operation is unambiguous.

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 the plan gate (Business and above, otherwise plan_required) and the required scope webhooks:read, which are real prerequisites for calling it. It also states the input must be the exact raw payload, which is a usage condition rather than a description of the resource. No explicit when-not guidance, but there is no plausible competing sibling.

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