Skip to main content
Glama

vibedeploy

by be.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

TableJSON Schema
NameRequiredDescriptionDefault
siteNameYesThe site whose custom sender domain to (re)check.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYes
statusYespending | verified | failed
lastErrorYes
dnsRecordsYes
request_idNoServer-assigned request correlation id. Quote it when contacting support.
spfVerifiedYes
dkimVerifiedYes

TDQS

A4.5/5.0
Behavior5/5

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

The description elaborates on behavior beyond annotations: it checks DNS, marks domain verified once DKIM record observed, switches to custom From with DKIM, falls back to platform address, and mentions DNS propagation delay. No contradiction with annotations.

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?

The description is concise: three sentences that each add value. First sentence states purpose, second details verification process and fallback, third gives propagation advice. No unnecessary words.

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?

Given the existing output schema and annotations, the description covers all necessary behavioral context: DNS check, verification effect, fallback, and retry guidance. It is complete for an idempotent DNS-checking tool.

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?

The schema has 100% coverage with a single parameter 'siteName' described as 'The site whose custom sender domain to (re)check.' The description echoes this with minimal added nuance (e.g., 'to (re)check'), so baseline score of 3 is appropriate.

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?

The description clearly states that the tool checks DNS records for a custom sender domain (DKIM TXT + SPF include). It distinguishes itself from siblings like verify_custom_domain by focusing on forms-specific sender domain verification.

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?

The description explains when to use the tool (for custom sender domains) and when not needed (when using custom smtpRelay). It also advises re-running if DNS propagation fails, providing clear context but not explicitly naming alternative tools.

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

All vibedeploy toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Every tool has a clearly distinct purpose, from deployment and file management to domain configuration and analytics. Even similar-sounding tools like add_files and add_file_chunk are well-differentiated by context and use case.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case (e.g., add_custom_domain, list_sites, delete_source_file). The naming is predictable and easy to understand.

Tool Count4/5

39 tools is higher than the typical 3-15 range, but each tool serves a necessary function for a comprehensive deployment platform. The count is justified by the broad feature set, though slightly heavy.

Completeness5/5

The tool set covers the full lifecycle of site deployment, management, backup, custom domains, form handling, analytics, and source editing. There are no obvious gaps for the intended functionality.

Resources