Skip to main content
Glama

Check a domain's mail DNS: SPF, DMARC, DKIM and more

dns
Read-only

Mail and DNS hygiene of a domain over DNS over HTTPS: A, AAAA, MX, NS, TXT and CAA records; SPF parsed (mechanisms, the all qualifier, a lookup estimate, a warning above 10 lookups); the DMARC policy; DKIM keys under common selectors; MTA-STS, TLS-RPT and BIMI; an issues list and a mail grade from A to F. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain or URL, e.g. example.com

Output Schema

NameRequiredDescriptionDefault
aNo
mxNo
nsNo
caaNo
spfNo
txtNo
aaaaNo
bimiNo
dkimNo
dmarcNo
domainNo
existsNo
issuesNo
mtaStsNo
nullMxNo
sourceNo
tlsRptNo
checkedAtNo
mailGradeNo
mailScoreNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "a": {},
      +    "aaaa": {},
      +    "bimi": {},
      +    "caa": {},
      +    "checkedAt": {},
      +    "dkim": {},
      +    "dmarc": {},
      +    "domain": {},
      +    "exists": {},
      +    "issues": {},
      +    "mailGrade": {},
      +    "mailScore": {},
      +    "mtaSts": {},
      +    "mx": {},
      +    "ns": {},
      +    "nullMx": {},
      +    "source": {},
      +    "spf": {},
      +    "tlsRpt": {},
      +    "txt": {}
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description still adds real behavioral context: a cost of $0.002 per successful call via x402 with failures uncharged, and an SPF lookup warning above 10 lookups. It does not state rate limits or latency, but the payment and failure semantics are exactly the kind of thing annotations can't convey.

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: the front-loaded purpose followed by an itemized coverage list, then a separate pricing sentence. The semicolon-delimited enumeration is dense but every item carries information about what is or isn't checked.

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 structure needn't be explained, and annotations cover the safety profile. With coverage, grading, warning thresholds and pricing all stated for a one-parameter read-only tool, nothing an agent needs before calling 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 a single parameter with 100% schema description coverage, so the schema already documents `domain` including that a URL is accepted. The description adds nothing about input handling (e.g. whether a full URL with path is normalized), which matches the baseline-3 expectation when the schema does the heavy lifting.

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?

The description names a specific resource set (A, AAAA, MX, NS, TXT, CAA, SPF, DMARC, DKIM, MTA-STS, TLS-RPT, BIMI) and a concrete outcome (issues list plus an A–F mail grade), so an agent can tell this is a mail/DNS posture audit rather than a generic lookup. It never names the sibling `domain` or states how it differs from it, so differentiation is inferred from the record list rather than asserted.

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 enumerated coverage — you call this when you want mail authentication and DNS hygiene for a domain. There is no explicit when-to-use/when-not statement and no pointer to a sibling for general domain data, so the agent must infer the boundary itself.

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