Skip to main content
Glama

AgentMart

by ai.ciphyr.agentmart
OverviewDiscussionsAdmin

Set webhook inbox pro forwarding, signature checks and handshakes

inbox_pro_set
DestructiveIdempotent

Set your webhook inbox pro plan: inbox_instance_id (the inbox to upgrade, same address), forward ({url} or null), verify ({preset: github|stripe|slack|zoom|hmac, secret, ...} or null), handshakes ({slack, zoom, meta_verify_token}). Fields left out stay. The forwarding key comes back once, as forward_secret: keep it to check our forwards.

Input Schema

NameRequiredDescriptionDefault
verifyNoSender signature check; null turns it off.
forwardNoWhere to forward every message; null turns it off.
handshakesNoAnswer the Slack, Zoom or Meta URL checks.
instance_idYesUtility instance id from buy or list_utilities.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.
inbox_instance_idNoThe inbox to upgrade (one of yours).
rotate_forward_secretNotrue: a new forwarding key (returned once).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "inbox_instance_id": "inb_exampleexampleexample2",
+    "instance_id": "ipr_exampleexampleexample2",
+    "verify": {
+      "preset": "github",
+      "secret": "example-secret"
+    }
+  }
+]
    • addedInput schema / properties / handshakes / properties / meta_verify_token / description
      Added value: +"Answer Meta's GET hub.challenge when hub.verify_token equals this (8 to 256 characters). null turns it off."
    • addedInput schema / properties / handshakes / properties / slack / description
      Added value: +"Answer Slack's url_verification (needs verify preset slack)."
    • addedInput schema / properties / handshakes / properties / zoom / description
      Added value: +"Answer Zoom's endpoint.url_validation (needs verify preset zoom)."
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
    • changedInput schema / properties / verify / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "algorithm": {
-        "enum": [
-          "sha256",
-          "sha512",
-          "sha1"
-        ],
-        "type": "string"
-      },
-      "encoding": {
-        "enum": [
-          "hex",
-          "base64"
-        ],
-        "type": "string"
-      },
-      "forward_only_verified": {
-        "description": "true: forward only messages whose signature verified; the rest stay in the inbox (forward status skipped, not_verified).",
-        "type": "boolean"
-      },
-      "header": {
-        "description": "hmac only: the signature header.",
-        "maxLength": 100,
-        "minLength": 1,
-        "type": "string"
-      },
-      "prefix": {
-        "maxLength": 20,
-        "type": "string"
-      },
-      "preset": {
-        "enum": [
-          "github",
-          "stripe",
-          "slack",
-          "zoom",
-          "hmac"
-        ],
-        "type": "string"
-      },
-      "reject_unverified": {
-        "type": "boolean"
-      },
-      "secret": {
-        "description": "The sender's signing secret (stored encrypted, never shown).",
-        "maxLength": 256,
-        "minLength": 1,
-        "type": "string"
-      }
-    },
-    "required": [
-      "preset",
-      "secret"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "algorithm": {
+        "description": "hmac only, default sha256.",
+        "enum": [
+          "sha256",
+          "sha512",
+          "sha1"
+        ],
+        "type": "string"
+      },
+      "encoding": {
+        "description": "hmac only, default hex.",
+        "enum": [
+          "hex",
+          "base64"
+        ],
+        "type": "string"
+      },
+      "forward_only_verified": {
+        "description": "true: forward only messages whose signature verified; the rest stay in the inbox (forward status skipped, not_verified).",
+        "type": "boolean"
+      },
+      "header": {
+        "description": "hmac only: the signature header.",
+        "maxLength": 100,
+        "minLength": 1,
+        "type": "string"
+      },
+      "prefix": {
+        "description": "hmac only: text before the signature, for example \"sha256=\".",
+        "maxLength": 20,
+        "type": "string"
+      },
+      "preset": {
+        "description": "The sender: github, stripe, slack or zoom, or hmac for any other sender that signs with HMAC.",
+        "enum": [
+          "github",
+          "stripe",
+          "slack",
+          "zoom",
+          "hmac"
+        ],
+        "type": "string"
+      },
+      "reject_unverified": {
+        "description": "true: a message that fails is refused with 401 and not stored.",
+        "type": "boolean"
+      },
+      "secret": {
+        "description": "The sender's signing secret (stored encrypted, never shown).",
+        "maxLength": 256,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "preset",
+      "secret"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Changed1 schema field changed
    • changedInput schema / properties / verify / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "algorithm": {
-        "enum": [
-          "sha256",
-          "sha512",
-          "sha1"
-        ],
-        "type": "string"
-      },
-      "encoding": {
-        "enum": [
-          "hex",
-          "base64"
-        ],
-        "type": "string"
-      },
-      "header": {
-        "description": "hmac only: the signature header.",
-        "maxLength": 100,
-        "minLength": 1,
-        "type": "string"
-      },
-      "prefix": {
-        "maxLength": 20,
-        "type": "string"
-      },
-      "preset": {
-        "enum": [
-          "github",
-          "stripe",
-          "slack",
-          "zoom",
-          "hmac"
-        ],
-        "type": "string"
-      },
-      "reject_unverified": {
-        "type": "boolean"
-      },
-      "secret": {
-        "description": "The sender's signing secret (stored encrypted, never shown).",
-        "maxLength": 256,
-        "minLength": 1,
-        "type": "string"
-      }
-    },
-    "required": [
-      "preset",
-      "secret"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "algorithm": {
+        "enum": [
+          "sha256",
+          "sha512",
+          "sha1"
+        ],
+        "type": "string"
+      },
+      "encoding": {
+        "enum": [
+          "hex",
+          "base64"
+        ],
+        "type": "string"
+      },
+      "forward_only_verified": {
+        "description": "true: forward only messages whose signature verified; the rest stay in the inbox (forward status skipped, not_verified).",
+        "type": "boolean"
+      },
+      "header": {
+        "description": "hmac only: the signature header.",
+        "maxLength": 100,
+        "minLength": 1,
+        "type": "string"
+      },
+      "prefix": {
+        "maxLength": 20,
+        "type": "string"
+      },
+      "preset": {
+        "enum": [
+          "github",
+          "stripe",
+          "slack",
+          "zoom",
+          "hmac"
+        ],
+        "type": "string"
+      },
+      "reject_unverified": {
+        "type": "boolean"
+      },
+      "secret": {
+        "description": "The sender's signing secret (stored encrypted, never shown).",
+        "maxLength": 256,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "preset",
+      "secret"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  4. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's job is to add specifics, which it partly does: 'Fields left out stay' discloses merge-not-replace semantics and 'The forwarding key comes back once, as forward_secret' discloses a one-time secret return that no output schema documents. It doesn't spell out what is actually destroyed (e.g. rotating invalidates the old key, null turns off forwarding), which is a gap given destructiveHint=true.

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?

Front-loads the verb and resource, then packs the field list and the two behavioral notes into a tight, semicolon-delimited sentence set with no filler. Minor cost: 'same address' for inbox_instance_id is opaque and briefly slows the reader.

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 7-parameter mutation tool with nested objects and no output schema, the description covers what can be set, that omitted fields persist, and the one returned value an agent must capture (forward_secret). Annotations carry the safety profile, so the remaining omissions (auth fallback, rotation consequences) are secondary.

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 nested verify/forward/handshakes properties are documented in detail in the schema itself, so the schema already does the heavy lifting. The description restates the same shapes at a glance (preset list, {url} or null) but adds no semantics beyond it; baseline 3 applies.

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?

States a specific verb ('Set') and resource ('your webhook inbox pro plan') and enumerates exactly which fields are configurable: forwarding, signature verification and handshakes. The 'Set' framing plainly contrasts with the read-side sibling inbox_pro_get, so an agent can pick between them without opening either schema.

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 implied by the field list: call this to configure forwarding, verification or handshakes, and 'Fields left out stay' signals partial-update semantics. But nothing states when NOT to use it, when to pair it with inbox_pro_get, or when rotate_forward_secret/passport_token matter, so the agent must infer routing.

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

All AgentMart toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources