Skip to main content
Glama

Email Auth Check - SPF, DKIM, DMARC, MX, MTA-STS, BIMI

email_auth
Read-onlyIdempotent

Email deliverability and spoofing check for a domain in one call: MX + mail provider, SPF (all qualifier, DNS lookup count vs the limit of 10), DMARC policy/pct/reporting, DKIM keys on 20+ common selectors (or yours), MTA-STS, TLS-RPT and BIMI, with a 0-100 score, grade, plain-English issues and, for every lost point, the exact DNS record to publish (name + TXT value, MTA-STS policy file). Live DNS, ~1 s. Free: 25 calls/day per IP. Paid: $0.002 per call via x402 at https://radarbg.com/x402/email-auth.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "github.com"
    },
    "name": "email_auth"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain or email address, e.g. example.com or info@example.com
dkimSelectorsNoExtra DKIM selectors to check, comma separated, e.g. s2048,mailchimp

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations only declare readOnly/openWorld/idempotent; the description adds substantial context beyond them: live DNS resolution, ~1 s latency, a 25 calls/day free cap per IP, and paid pricing via x402 with an endpoint URL. It also discloses the return shape (0-100 score, grade, plain-English issues, exact DNS records to publish) despite there being no output schema.

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 capability list is front-loaded and the operational facts (latency, quota, pricing) come last in a compact second sentence. It is dense but each clause carries distinct information; the only cost is a long single sentence that is harder to skim than a short bulleted breakdown.

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 no output schema, the description still tells the agent what comes back (score, grade, issues, and per-point DNS remediation records including MTA-STS policy files). Cost, rate limit, latency, and data freshness (live DNS) are all covered, leaving nothing an agent needs before calling.

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 description coverage is 100%, so both parameters are already documented in structured data and the baseline of 3 applies. The description contributes a little extra meaning for dkimSelectors ("20+ common selectors (or yours)"), but does not repeat or expand the schema's note that the domain parameter also accepts a full email address.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb-and-resource framing ("email deliverability and spoofing check for a domain in one call") followed by an exhaustive enumeration of what is checked: MX/provider, SPF qualifier and lookup count, DMARC, DKIM selectors, MTA-STS, TLS-RPT, BIMI. The enumeration makes the scope unmistakable versus generic siblings like domain_intel or website_report, though no sibling is named explicitly to sharpen the boundary.

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

Usage Guidelines3/5

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

Usage is implied by the stated purpose (auditing a domain's email authentication posture) and reinforced by the "one call" framing, so an agent can tell when it fits. However, there is no when-not guidance and no contrast with adjacent tools such as domain_security_report or domain_intel, which the agent must disambiguate on its own.

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.

Resources