Skip to main content
Glama
RevClamp MCP Server

RevClamp MCP Server

revclamp_simulate_webhook_replay

Simulate out-of-order and duplicate subscription lifecycle webhooks to test 72-hour deduplication and createdSec watermark ordering against a naive arrival-order handler.

Instructions

Simulates out-of-order and duplicate subscription lifecycle webhooks against a 72-hour deduplication Set and monotonic createdSec watermark vs. a naive arrival-order handler.

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

Input Schema

NameRequiredDescriptionDefault
demoNo
eventsNo
nowSecNo
scenarioPresetNoout_of_order_stale_update_after_cancel
idempotencyWindowSecNo

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 disclose meaningful mechanics: a 72-hour deduplication window and a monotonic createdSec watermark compared against a naive arrival-order handler. However, it never states that this is a side-effect-free simulation (no real webhooks delivered or state mutated), whether it requires auth, or what the response looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence, front-loaded with the verb and resource, with zero filler. The trailing "vs. a naive arrival-order handler" earns its place by framing the comparison the simulation performs.

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?

For a five-parameter simulation tool with no annotations and no output schema, the description is thin: it does not explain the return value (no output schema exists to do so), the demo and nowSec controls, the scenarioPreset choices, or the shape of event objects. An agent could not reliably construct a correct call from this definition alone.

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 the description must compensate. It adds real meaning for the key parameters by explaining the 72-hour dedup window (idempotencyWindowSec), the createdSec watermark, and out-of-order/duplicate arrival semantics (arrivedAtSec). It does not explain demo, nowSec, the scenarioPreset enum values, or the event object fields, so compensation is only partial across the five parameters.

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 ("Simulates") and a specific resource (out-of-order and duplicate subscription lifecycle webhooks) plus the mechanism under test (72-hour dedup Set and monotonic createdSec watermark vs. naive arrival-order handler). The purpose is clear enough to distinguish it from the signature-verification, leakage-audit, and reconciliation siblings, though it never names an alternative explicitly.

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 statement of when to use this tool, when not to, or what it should be preferred over. The scenarioPreset default hints at a testing/simulation use case, but an agent gets no guidance on choosing this tool versus any other revclamp tool, nor on prerequisites or expected workflow.

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