Skip to main content
Glama

OmniForge Launch Audit MCP

SPF, DKIM, DMARC & DNSBL Email Deliverability Audit

audit_email_deliverability
Read-onlyIdempotent

Audit a sending domain's email authentication and inbox placement health: resolves MX servers, recursively counts SPF DNS lookups against the RFC 7208 10-lookup hard limit, probes 18 standard ESP DKIM selectors, validates DMARC policy enforcement, checks MTA-STS/BIMI, and tests the primary mail IP against major DNSBL blacklists. Use this tool for diagnosing why transactional or marketing emails land in spam; use full_launch_readiness_audit when also checking brand conflicts and AI search crawlers.

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": {
      "domain": "<domain>"
    },
    "name": "audit_email_deliverability"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesTarget sending domain to inspect (e.g. 'stripe.com' or 'acme.io').

Output Schema

NameRequiredDescriptionDefault
spfYesSPF record text and recursive DNS lookup count.
dkimNoDiscovered active DKIM selectors.
dmarcYesDMARC record and enforcement policy.
gradeYesLetter grade from A to D.
scoreYes0-100 Deliverability Readiness Score.
domainYesNormalized domain name.
issuesYesActionable DNS authentication issues.
checkedAtYesISO-8601 UTC timestamp.
mxRecordsNoOrdered MX hostnames.
blacklistsNoDNSBL blacklists flagging the primary MX IP.
upgradeLinksNoLinks for automatic SPF flattening and 24/7 drift alerts.
detectedProviderYesDetected email service provider (Google Workspace, Microsoft 365, Resend, Amazon SES, etc.).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description still earns credit by disclosing the concrete probing behavior an agent could not infer: recursive SPF lookup counting against the RFC 7208 hard limit, 18 standard ESP DKIM selectors, and live DNSBL checks against major blacklists. It does not mention latency or external-query volume, which keeps it short of a 5.

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?

Two sentences, zero filler: the first front-loads scope and the specific probes, the second handles routing. The dense enumeration is appropriate because each item is a distinct capability an agent may need to justify selection.

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 no explanation, and annotations carry the safety and openness profile. With the single parameter fully documented and the audit's method and routing both stated, nothing an agent needs to call this correctly is missing.

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 one parameter and schema description coverage is 100%; the schema already defines `domain` with a format example. The description reinforces that it is a sending domain but adds no syntax, normalization, or edge-case guidance beyond the schema, so the 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?

Specific verb ("Audit") plus a precisely scoped resource ("a sending domain's email authentication and inbox placement health"), then an enumeration of the exact checks performed: MX, SPF lookup counting, DKIM selector probing, DMARC, MTA-STS/BIMI, DNSBL. An agent can distinguish this from the sibling audits without reading any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use case ("diagnosing why transactional or marketing emails land in spam") and names the alternative tool plus the exact condition that selects it ("when also checking brand conflicts and AI search crawlers"). Both when-to-use and when-to-prefer-a-sibling are stated.

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.