VibeDeploy

Verify a forms custom sender domain

verify_forms_sender_domain

Idempotent

Check the DNS records for a site's custom sender domain (DKIM TXT + SPF include). Once the DKIM record is observed, the sender domain is marked verified and the relay sends from the custom From (DKIM-signed). Until then it falls back to the platform address. DNS can take a few minutes to propagate; re-run if it fails the first time. Not needed when the site uses a custom smtpRelay.

Input Schema

Name	Required	Description	Default
`siteName`	Yes	The site whose custom sender domain to (re)check.

Output Schema

Name	Required	Description
`domain`	Yes
`status`	Yes	pending \| verified \| failed
`lastError`	Yes
`dnsRecords`	Yes
`spfVerified`	Yes
`dkimVerified`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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.5/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the resulting state change: once DKIM is observed the domain is marked verified and mail relays from the DKIM-signed custom From, otherwise it falls back to the platform address. The annotations mark this non-read-only and idempotent, and the description explains exactly what mutates and confirms safe re-running.

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?

Four tight sentences, front-loaded with the verification action, then the outcome, then operational timing advice, ending with the exclusion. No filler and every sentence contributes actionable information.

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?

An output schema exists, so return values need not be described. For a state-mutating verification tool the description covers the trigger, the consequence, fallback behavior, retry guidance, and the case where it isn't needed at all.

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?

Only one parameter with 100% schema description coverage, so the schema already carries the semantics; the description merely implies that the site's sender domain is the target and that the check is repeatable. Baseline 3 applies when the schema does the heavy lifting.

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 precise verb and resource: checking DNS records (DKIM TXT + SPF include) for a site's custom sender domain. This is clearly distinguished from the sibling verify_custom_domain, which concerns hostname DNS rather than sender-domain DKIM/SPF records.

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?

Gives an explicit exclusion ('Not needed when the site uses a custom smtpRelay') and practical timing guidance ('DNS can take a few minutes to propagate; re-run if it fails'). It does not name a sibling tool to use instead for other verification needs, but the when/when-not framing is clear.

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.