Skip to main content
Glama
RevClamp MCP Server

RevClamp MCP Server

revclamp_verify_webhook_signature

Verifies HMAC-SHA256 webhook signatures for Stripe, Shopify, and RevClamp, with timestamp replay protection.

Instructions

Generates and verifies raw-UTF8 HMAC-SHA256 webhook signatures for Stripe (Stripe-Signature t=,v1=), Shopify (X-Shopify-Hmac-Sha256 base64), and RevClamp (X-RevClamp-Signature) with 300s timestamp replay protection.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "revclamp_verify_webhook_signature"
  }
}

Input Schema

NameRequiredDescriptionDefault
demoNo
secretNo
secretsNo
providerNo
rawPayloadNo
timestampSecNo
toleranceSecNo
signatureHeaderNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.20.29

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does supply real protocol detail: raw-UTF8 HMAC-SHA256, per-provider header shapes (t=,v1= for Stripe; base64 for Shopify), and a 300s replay window. It says nothing about what happens on a mismatch (error vs. boolean), whether it is constant-time, or any rate/auth constraints. That gap keeps it at adequate rather than strong.

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 no filler; the algorithm, providers, and replay window all appear immediately. The stacked parentheticals are dense but each carries concrete information. Slightly more structure (separating generate from verify) would improve scanability.

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 an 8-parameter tool with zero annotation and schema-description coverage and no output schema, the description covers the core signing protocol well but leaves the response contract and half the parameters undocumented. An agent could attempt a call from this text but would be guessing on secret selection and on what a failed verification returns.

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 0%, so all 8 parameters depend on the description, and it only partially compensates. It clarifies the provider-to-header mapping and the default 300s timestamp tolerance, which helps interpret provider, signatureHeader, and toleranceSec. It leaves demo, secret vs. secrets (multi-secret rotation), rawPayload, and timestampSec unexplained.

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 opens with a specific verb pair and resource ('Generates and verifies ... HMAC-SHA256 webhook signatures') and names the three supported providers plus their header formats. An agent can tell this is a signature-generation/verification utility rather than an audit or simulation tool. It stops short of 5 because it bundles two distinct operations (generate vs. verify) without stating which mode a given call takes, and it never distinguishes itself from the replay-simulation sibling.

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 explicit when-to-use or when-not-to-use guidance, and none of the siblings (e.g. revclamp_simulate_webhook_replay) are named as alternatives. The inbound-webhook context is only implied by the provider header formats. An agent must infer that this is the tool for validating an incoming signature rather than replay-testing one.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.