Skip to main content
Glama

MailAuth Audit (Email Deliverability)

audit_mailauth

Read-onlyIdempotent

Full email deliverability audit of a domain (bare domain, e.g. example.com). Resolves the domain's mail DNS over DNS-over-HTTPS and runs 12 weighted checks: MX presence and redundancy, SPF presence, validity (single record, <=10 DNS lookups), and terminal policy (-all vs ~all vs ?all), DMARC presence, enforcement policy (p=reject/quarantine/none, pct), and aggregate reporting (rua), DKIM discoverability at 10 common selectors, MTA-STS, TLS-RPT, and BIMI. These records decide whether receivers can verify mail claiming to be from the domain: no DMARC (or p=none) means the domain is trivially spoofable by anyone, and broken SPF/DKIM alignment is why legitimate mail lands in spam. Returns machine-readable JSON: 0-100 score, A-F grade, a spoofing/deliverability risk level (Low/Moderate/Elevated/High) with the failing spoofing-class checks named, per-check pass/partial/fail/unknown with evidence, the observed records (MX hosts, SPF record, DMARC policy/pct, DKIM selectors found, MTA-STS/TLS-RPT/BIMI presence), and the top 3 prioritized fixes. HONEST LIMITS: this is a DNS snapshot at scan time; DKIM is probed at common selectors only (a custom selector reads as undiscoverable, not absent); no mail is sent, and inbox placement is not guaranteed. Cost: $1.50 USDC on Base per call, paid via x402 — the caller's agent pays from its owner's approved wallet; no API key needed. Use this before launching outbound from a domain, after any DNS change, or to triage a spoofing/spam-folder problem.

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_mailauth"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesBare domain to audit, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare read-only, open-world, idempotent, non-destructive; the description adds what those cannot: a $1.50 USDC x402 payment with no API key, and an explicit HONEST LIMITS block (DNS snapshot at scan time, DKIM probed only at common selectors so a custom selector reads as undiscoverable rather than absent, no mail sent, no placement guarantee). That is exactly the kind of disclosure an agent needs before spending money or acting on results.

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?

Long but front-loaded: purpose first, then checks, then return shape, then limits and cost. The middle rationale about DMARC p=none and SPF/DKIM alignment is explanatory value rather than pure necessity, and the whole body is one undivided block, which makes it harder to scan than it needs to be.

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?

With a single required parameter and no output schema, the description carries the full burden and does so: it describes the JSON return (score, grade, risk level, per-check status with evidence, observed records, top 3 fixes), the cost mechanism, and the interpretive limits. Nothing needed to call or to interpret the result 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?

Schema coverage is 100% and there is only one parameter, so the schema already documents 'domain' with the same example. The description's 'bare domain, e.g. example.com' restates rather than extends the schema; the surrounding audit context does not add per-parameter meaning.

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 and resource ('full email deliverability audit of a domain') and enumerates exactly what is checked: MX, SPF, DMARC, DKIM selectors, MTA-STS, TLS-RPT, BIMI. An agent can distinguish this from a generic DNS lookup without opening the schema.

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 three concrete triggers — before launching outbound from a domain, after any DNS change, and to triage spoofing or spam-folder problems. It does not name when to prefer the lite sibling or when this audit is overkill, so routing between the two is left to inference.

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.