VibeDeploy

Enable or update the forms relay for a site

set_forms_config

DestructiveIdempotent

Configure the built-in form-to-email relay, fully self-service. Supports a custom From (via a verified sender domain or your own SMTP relay), an explicit Reply-To, and full email branding (subject template, field labels/order, logo, accent color, or a custom HTML body). Requires team role owner or admin. Pass config:null to switch the relay off. If you set a custom sender without an smtpRelay, the response returns the DNS records to publish; then call verify_forms_sender_domain. Submissions: POST JSON to the returned endpoint with Content-Type: application/json (UTF-8). Flat object of form fields (strings/numbers/booleans; checkbox groups may be arrays of strings, joined with ', '). Max 30 fields, 5000 chars/field, 20000 total. Response: {success:true,data:{ok:true}} or {success:false,error:{code,message}}. Rate limit: 10 submits per IP per 10 minutes. Include a hidden honeypot input (default "_gotcha") and leave it empty.

Input Schema

Name	Required	Description	Default
`config`	Yes	Full config to store (replaces existing). Pass null to disable and clear.
`siteName`	Yes	The site to configure.

Output Schema

Name	Required	Description
`notes`	Yes
`enabled`	Yes
`delivery`	Yes	platform \| verified-domain \| verified-domain-pending \| custom-relay.
`endpoint`	Yes	URL the site's form should POST to.
`siteName`	Yes
`formsConfig`	Yes	Stored config (smtpRelay.password redacted to hasPassword).
`activeSender`	Yes	The From that will actually be used right now.
`senderDomain`	No	DNS records to publish + verification status (verified-domain path).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

changedInput schema / properties / config / anyOf

Previous value: -[
-  {
-    "properties": {
-      "allowedOrigins": {
-        "description": "Extra origins allowed to POST. The site's own domains are always allowed.",
-        "items": {
-          "type": "string"
-        },
-        "maxItems": 10,
-        "type": "array"
-      },
-      "confirmation": {
-        "description": "Optional confirmation email to the visitor.",
-        "properties": {
-          "emailField": {
-            "description": "Form field with the visitor email. Default \"email\".",
-            "maxLength": 100,
-            "type": "string"
-          },
-          "enabled": {
-            "type": "boolean"
-          },
-          "message": {
-            "maxLength": 2000,
-            "type": "string"
-          },
-          "subject": {
-            "maxLength": 200,
-            "type": "string"
-          }
-        },
-        "required": [
-          "enabled"
-        ],
-        "type": "object"
-      },
-      "enabled": {
-        "description": "Master switch. false keeps the config but the endpoint returns 404.",
-        "type": "boolean"
-      },
-      "honeypotField": {
-        "description": "Hidden field that must stay empty. Default \"_gotcha\".",
-        "maxLength": 100,
-        "type": "string"
-      },
-      "recipients": {
-        "description": "Server-side fixed lead recipients (1-5).",
-        "items": {
-          "type": "string"
-        },
-        "maxItems": 5,
-        "minItems": 1,
-        "type": "array"
-      },
-      "replyTo": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "properties": {
-              "field": {
-                "maxLength": 100,
-                "type": "string"
-              }
-            },
-            "required": [
-              "field"
-            ],
-            "type": "object"
-          }
-        ],
-        "description": "Reply-To: \"visitor\" (default), \"none\", a fixed email, or { field: \"<formField>\" }."
-      },
-      "requiredFields": {
-        "items": {
-          "maxLength": 100,
-          "type": "string"
-        },
-        "maxItems": 30,
-        "type": "array"
-      },
-      "sender": {
-        "description": "Custom From sender.",
-        "properties": {
-          "email": {
-            "description": "From address, e.g. support@serso.be. Only honored once its domain is verified (verify_forms_sender_domain) OR an smtpRelay is set; otherwise mail falls back to the platform address.",
-            "type": "string"
-          },
-          "name": {
-            "description": "Display name, e.g. \"Serso Service Portal\".",
-            "maxLength": 100,
-            "type": "string"
-          }
-        },
-        "required": [
-          "email"
-        ],
-        "type": "object"
-      },
-      "smtpRelay": {
-        "description": "Deliver via your own SMTP server instead of the platform. Your server then owns SPF/DKIM. Recipients stay server-side — this is not an open relay.",
-        "properties": {
-          "allowInvalidCert": {
-            "description": "Accept a self-signed/mismatched cert (starttls|tls). Default false.",
-            "type": "boolean"
-          },
-          "host": {
-            "description": "SMTP server hostname or IP (must be public).",
-            "type": "string"
-          },
-          "password": {
-            "anyOf": [
-              {
-                "type": "string"
-              },
-              {
-                "type": "null"
-              }
-            ],
-            "description": "Set to store/replace (encrypted at rest). Omit to keep the existing one. null to clear. Never returned on read."
-          },
-          "port": {
-            "description": "SMTP port, e.g. 25, 26, 465, 587.",
-            "maximum": 9007199254740991,
-            "minimum": -9007199254740991,
-            "type": "integer"
-          },
-          "security": {
-            "description": "\"none\" = plaintext, \"starttls\" = upgrade, \"tls\" = implicit TLS.",
-            "enum": [
-              "none",
-              "starttls",
-              "tls"
-            ],
-            "type": "string"
-          },
-          "username": {
-            "description": "Omit for a no-auth trusted-host relay.",
-            "type": "string"
-          }
-        },
-        "required": [
-          "host",
-          "port",
-          "security"
-        ],
-        "type": "object"
-      },
-      "subject": {
-        "maxLength": 200,
-        "type": "string"
-      },
-      "template": {
-        "description": "Email branding / layout.",
-        "properties": {
-          "accentColor": {
-            "description": "#RRGGBB accent color.",
-            "type": "string"
-          },
-          "bodyHtml": {
-            "description": "Full custom HTML body with {fieldName} placeholders (values HTML-escaped). Overrides the generated table.",
-            "maxLength": 20000,
-            "type": "string"
-          },
-          "fieldLabels": {
-            "additionalProperties": {
-              "type": "string"
-            },
-            "description": "Map raw field name -> human label.",
-            "propertyNames": {
-              "type": "string"
-            },
-            "type": "object"
-          },
-          "fieldOrder": {
-            "description": "Display order; unlisted fields follow in submit order.",
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          "footerText": {
-            "maxLength": 2000,
-            "type": "string"
-          },
-          "headerText": {
-            "maxLength": 2000,
-            "type": "string"
-          },
-          "logoUrl": {
-            "description": "https logo URL shown in the email header.",
-            "type": "string"
-          },
-          "subjectTemplate": {
-            "description": "Subject with {fieldName} placeholders. Overrides `subject`.",
-            "maxLength": 200,
-            "type": "string"
-          }
-        },
-        "type": "object"
-      }
-    },
-    "required": [
-      "enabled",
-      "recipients"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "allowedOrigins": {
+        "description": "Extra origins allowed to POST. The site's own domains are always allowed.",
+        "items": {
+          "type": "string"
+        },
+        "maxItems": 10,
+        "type": "array"
+      },
+      "confirmation": {
+        "description": "Optional confirmation email to the visitor.",
+        "properties": {
+          "emailField": {
+            "description": "Form field with the visitor email. Default \"email\".",
+            "maxLength": 100,
+            "type": "string"
+          },
+          "enabled": {
+            "description": "Send the confirmation email.",
+            "type": "boolean"
+          },
+          "message": {
+            "description": "Text of the confirmation email.",
+            "maxLength": 2000,
+            "type": "string"
+          },
+          "subject": {
+            "description": "Subject of the confirmation email.",
+            "maxLength": 200,
+            "type": "string"
+          }
+        },
+        "required": [
+          "enabled"
+        ],
+        "type": "object"
+      },
+      "enabled": {
+        "description": "Master switch. false keeps the config but the endpoint returns 404.",
+        "type": "boolean"
+      },
+      "honeypotField": {
+        "description": "Hidden field that must stay empty. Default \"_gotcha\".",
+        "maxLength": 100,
+        "type": "string"
+      },
+      "recipients": {
+        "description": "Server-side fixed lead recipients (1-5).",
+        "items": {
+          "type": "string"
+        },
+        "maxItems": 5,
+        "minItems": 1,
+        "type": "array"
+      },
+      "replyTo": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "properties": {
+              "field": {
+                "description": "Form field that holds the Reply-To address.",
+                "maxLength": 100,
+                "type": "string"
+              }
+            },
+            "required": [
+              "field"
+            ],
+            "type": "object"
+          }
+        ],
+        "description": "Reply-To: \"visitor\" (default), \"none\", a fixed email, or { field: \"<formField>\" }."
+      },
+      "requiredFields": {
+        "description": "Form fields that must be filled in.",
+        "items": {
+          "maxLength": 100,
+          "type": "string"
+        },
+        "maxItems": 30,
+        "type": "array"
+      },
+      "sender": {
+        "description": "Custom From sender.",
+        "properties": {
+          "email": {
+            "description": "From address, e.g. support@example.com. Used once its domain is verified (verify_forms_sender_domain) or an smtpRelay is set; until then mail uses the platform address.",
+            "type": "string"
+          },
+          "name": {
+            "description": "Display name, e.g. \"Acme Support\".",
+            "maxLength": 100,
+            "type": "string"
+          }
+        },
+        "required": [
+          "email"
+        ],
+        "type": "object"
+      },
+      "smtpRelay": {
+        "description": "Deliver via your own SMTP server instead of the platform. Your server then owns SPF/DKIM. Recipients stay server-side, so this is not an open relay.",
+        "properties": {
+          "allowInvalidCert": {
+            "description": "Accept a self-signed/mismatched cert (starttls|tls). Default false.",
+            "type": "boolean"
+          },
+          "host": {
+            "description": "SMTP server hostname or IP (must be public).",
+            "type": "string"
+          },
+          "password": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Set to store/replace (encrypted at rest). Omit to keep the existing one. null to clear. Never returned on read."
+          },
+          "port": {
+            "description": "SMTP port, e.g. 25, 26, 465, 587.",
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "security": {
+            "description": "\"none\" = plaintext, \"starttls\" = STARTTLS on a plain connection, \"tls\" = implicit TLS.",
+            "enum": [
+              "none",
+              "starttls",
+              "tls"
+            ],
+            "type": "string"
+          },
+          "username": {
+            "description": "Omit for a no-auth trusted-host relay.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "host",
+          "port",
+          "security"
+        ],
+        "type": "object"
+      },
+      "subject": {
+        "description": "Subject of the lead email.",
+        "maxLength": 200,
+        "type": "string"
+      },
+      "template": {
+        "description": "Email branding / layout.",
+        "properties": {
+          "accentColor": {
+            "description": "#RRGGBB accent color.",
+            "type": "string"
+          },
+          "bodyHtml": {
+            "description": "Full custom HTML body with {fieldName} placeholders (values HTML-escaped). Overrides the generated table.",
+            "maxLength": 20000,
+            "type": "string"
+          },
+          "fieldLabels": {
+            "additionalProperties": {
+              "type": "string"
+            },
+            "description": "Map raw field name -> human label.",
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "fieldOrder": {
+            "description": "Display order; unlisted fields follow in submit order.",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "footerText": {
+            "description": "Text below the submitted fields.",
+            "maxLength": 2000,
+            "type": "string"
+          },
+          "headerText": {
+            "description": "Text above the submitted fields.",
+            "maxLength": 2000,
+            "type": "string"
+          },
+          "logoUrl": {
+            "description": "https logo URL shown in the email header.",
+            "type": "string"
+          },
+          "subjectTemplate": {
+            "description": "Subject with {fieldName} placeholders. Overrides `subject`.",
+            "maxLength": 200,
+            "type": "string"
+          }
+        },
+        "type": "object"
+      }
+    },
+    "required": [
+      "enabled",
+      "recipients"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed1 schema field changedSep 6, 2026

removedOutput schema / properties / request_id

Removed value: -{
-  "description": "Server-assigned request correlation id. Quote it when contacting support.",
-  "type": "string"
-}

Changed1 schema field changedJul 20, 2026

addedOutput schema / properties / request_id

Added value: +{
+  "description": "Server-assigned request correlation id. Quote it when contacting support.",
+  "type": "string"
+}

First observedJun 29, 2026

TDQS

A4.3/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. The description adds value beyond them by disclosing the auth requirement (owner/admin), replacement semantics ('Full config... replaces existing'), and the disable/clear behavior of null.

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-loaded with purpose and next-step before details. It is on the long side because it carries submission mechanics (POST JSON, field/char limits, honeypot, rate limit) that are tangential to invoking the config tool, but the structure is logical.

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?

With annotations covering the safety profile and an output schema present, the description need not restate returns. It covers auth, replacement behavior, and the verification workflow, leaving little an agent needs to call it correctly.

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. The description still adds meaning: it groups the config surface (custom From via verified domain or SMTP relay, Reply-To, branding) and explains the sender-without-smtpRelay DNS-record flow.

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+resource: 'Configure the built-in form-to-email relay.' It is easily distinguished from siblings get_forms_config (read) and verify_forms_sender_domain (verification), and even states the disable case ('config:null to switch the relay off').

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?

Clear context and prerequisites ('Requires team role owner or admin') and an explicit next-step route ('then call verify_forms_sender_domain'). It does not explicitly name get_forms_config as the read alternative, so it stops short of full when-not/alternative guidance.

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

All VibeDeploy tools Inspect

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.