Skip to main content
Glama
GrowSurf MCP Server

GrowSurf MCP Server

Official

Normalize Webhook Payload

growsurf_webhook_normalize
Read-onlyIdempotent

Validates and normalizes GrowSurf webhook payloads, then generates a best-effort idempotency key for deduplication.

Instructions

Validate/normalize a GrowSurf webhook payload and generate a best-effort idempotency key for dedupe.

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": {
      "payload": "<payload>"
    },
    "name": "growsurf_webhook_normalize"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYesJSON value to validate. A valid webhook envelope is an object with `event`, `createdAt`, and `data`. Other JSON values return `ok: false`.

Output Schema

NameRequiredDescriptionDefault
okNoWhether the payload is a valid GrowSurf webhook envelope.
errorNoWhy the payload failed validation. Present only when `ok` is `false`.
envelopeNoThe normalized webhook envelope. Present only when `ok` is `true`.
idempotencyKeyNoA key for ignoring duplicate deliveries: the event `id` when the payload has one, otherwise a key built from the event fields. Present only when `ok` is `true`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.19.34
    • addedOutput schema / properties / envelope / properties / id
      Added value: +{
      +  "description": "The event ID (e.g. `evt_...`). The same event keeps it on every retry and every webhook it is sent to. Absent on payloads that have none.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / idempotencyKey / description
      Previous value: -"A deterministic key for ignoring duplicate deliveries. Present only when `ok` is `true`."New value: +"A key for ignoring duplicate deliveries: the event `id` when the payload has one, otherwise a key built from the event fields. Present only when `ok` is `true`."
  2. Changed2 schema fields changedv0.19.9
    • addedInput schema / properties / payload / description
      Added value: +"JSON value to validate. A valid webhook envelope is an object with `event`, `createdAt`, and `data`. Other JSON values return `ok: false`."
    • addedInput schema / properties / payload / type
      Added value: +[
      +  "object",
      +  "array",
      +  "string",
      +  "number",
      +  "boolean",
      +  "null"
      +]
  3. First observedv0.12.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description does add genuinely useful qualifiers beyond the annotations - "best-effort" warns that the idempotency key is not guaranteed stable or unique, and "normalize" flags that the result is a transformed value - but it says nothing about what normalization actually does or when the key should be distrusted.

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?

One sentence, front-loaded with the primary verb, no filler, no restatement of the title. Everything it says is load-bearing.

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

Completeness4/5

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

For a single-parameter, read-only utility with an output schema and full annotation coverage, this is close to sufficient - the agent knows what goes in and that the result is a normalized payload plus a dedupe key. The only real gap is that "normalize" and "best-effort key" are left undefined, which matters if an agent must decide whether to trust the key across payload variants.

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 100% and the single payload parameter is fully documented, including the valid webhook envelope shape (`event`, `createdAt`, `data`) and the `ok: false` outcome for other JSON values. The description adds no parameter meaning beyond that, so baseline 3 is correct.

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 ("Validate/normalize") plus the resource ("GrowSurf webhook payload") and a secondary effect ("generate a best-effort idempotency key for dedupe"). That is enough to tell it apart from the surrounding create/delete/test webhook tools, though the description never explicitly frames it as the payload-inspection counterpart to those subscription-management siblings.

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?

Usage is only implied: "for dedupe" hints that this is what you call on an inbound webhook to check validity before acting on it. There is no explicit when-to-use statement, no prerequisite (e.g. call before create/test webhook flows), and no named alternative for agents that expected this tool to register or send webhooks.

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

Deploy Server

Other Tools