Skip to main content
Glama

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.

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": {
      "siteName": "<siteName>"
    },
    "name": "verify_forms_sender_domain"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
domainYes
statusYespending | verified | failed
lastErrorYes
dnsRecordsYes
spfVerifiedYes
dkimVerifiedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / lastError / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / lastError / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Changed1 schema field changed
    • removedOutput schema / properties / request_id
      Removed value: -{
      -  "description": "Server-assigned request correlation id. Quote it when contacting support.",
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • addedOutput schema / properties / request_id
      Added value: +{
      +  "description": "Server-assigned request correlation id. Quote it when contacting support.",
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

The annotations cover safety and idempotency (readOnlyHint=false, idempotentHint=true, destructiveHint=false), and the description goes well beyond them. It explains the state change (the domain is marked verified, and the relay then sends DKIM-signed from the custom From), the fallback behavior until verification, expected propagation delay, and retry guidance. None of this contradicts the mutable, idempotent, open-world annotations.

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?

The description is front-loaded with the core action and then layers on outcome, timing, and exclusion in short clauses. Every sentence is informative, though the passage is fairly dense with parentheticals and could be tightened slightly.

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 one-parameter verification tool with an output schema and rich annotations, the description covers everything needed to call it correctly: what is checked, what the result means, fallback behavior, timing, and when not to call it.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains siteName. The description reinforces which site and which domain are involved and adds the re-check connotation, but it gives no extra syntax or format detail beyond the schema; this matches the baseline of 3.

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 names a specific verb and resource: it checks DNS records (DKIM TXT + SPF include) for a site's custom forms sender domain. That is more specific than the sibling verify_custom_domain, which the description implicitly distinguishes by limiting scope to the forms sender domain and the smtpRelay exception.

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 clearly says when to run it (to check or re-check the sender domain) and explicitly excludes one case: 'Not needed when the site uses a custom smtpRelay.' It also tells the agent to re-run if the first attempt fails because of DNS propagation. It does not name a specific sibling tool as the alternative, which keeps it at a 4 rather than a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.