Skip to main content
Glama

Check a domain's mail and DNS health (MX, SPF, DKIM, DMARC, certificate)

domain_health_check
Read-onlyIdempotent

Mail and DNS health of a domain. Send a domain name; get six checks (MX records, SPF, DKIM selector hints, DMARC policy, TLS certificate expiry, public blocklists), each pass, fail or unknown with the record we saw and what to do, plus a signed, dated observation. Free, no sign-up, 100 checks a day per caller. Public DNS and one TLS handshake on port 443 only: no port scans, no mailbox probing, nothing stored. DKIM selectors cannot be listed, so a missing selector is unknown, never fail. Checks the domain you name, not who runs it.

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": "domain_health_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesA domain name such as example.com. Not a URL, address or email.
dkim_selectorsNoOptional DKIM selector names you use (the part before ._domainkey). We also try 12 common ones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world behavior, so the bar is lower; the description still adds real value with the 100-checks-per-day limit, the no-storage guarantee, the 443-only network footprint, and the crucial rule that a missing DKIM selector is 'unknown, never fail'. That last point materially changes how an agent should interpret 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?

Front-loaded with purpose and output shape, and every sentence carries information (checks, verdicts, rate limit, footprint, DKIM caveat). It is a dense single block with several clauses packed per sentence, which slightly impedes scanning, but there is no filler.

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?

No output schema exists, yet the description fully characterizes the return (six named checks, pass/fail/unknown, the record observed, remediation guidance, a signed dated observation). For a two-parameter read-only tool with annotations present, nothing an agent needs to call or interpret it 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?

Schema coverage is 100%, so both parameters are already documented, and the description adds only marginal semantics: that the service also tries 12 common selectors beyond those supplied. The 'selector cannot be listed, so missing means unknown' rule is useful but pertains more to result interpretation than to 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 the resource (mail and DNS health of a domain) and enumerates the six concrete checks returned, so an agent knows exactly what it gets. The closing line 'Checks the domain you name, not who runs it' actively separates it from identity/agency-style siblings.

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 clear conditions for use (a domain whose mail/DNS posture you want to assess) and explicit non-goals: no port scans, no mailbox probing, one TLS handshake on 443, nothing stored. It stops short of naming a specific alternative tool to use for other cases, so it lands at 4 rather than 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.

Resources