Skip to main content
Glama

Email authentication posture (SPF, DMARC, MTA-STS)

domain_email_auth
Read-only

Email authentication posture of a domain from DNS (Cloudflare DNS over HTTPS): MX records and null MX, SPF parsed into mechanisms with its all qualifier and a recursive DNS-lookup count against the RFC 7208 limit of 10, DMARC policy (p, sp, pct, alignment, report addresses' domains), MTA-STS and TLS-RPT records, and BIMI. DKIM is not assessed because selectors cannot be enumerated. Returns an A-F grade and 0-100 score with weighted reasons. Price: $0.003 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing 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": "domain_email_auth"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesBare domain, hostname, email address or URL. Scheme, path, port and credentials are stripped and IDNs are converted to punycode. IP addresses and private names are rejected.

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 readOnlyHint and openWorldHint; the description adds substantial context beyond that: the data source (Cloudflare DoH), the return shape (A-F grade, 0-100 score, weighted reasons), a concrete limitation (DKIM selectors cannot be enumerated), and detailed billing behavior including that failed or no-match calls are free. These are exactly the traits an agent needs before invoking a paid external call.

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 first sentence is a dense but well-ordered inventory of what is checked, followed by scope exclusion, output shape, and pricing. Every sentence carries information, though the long enumeration sentence and trailing price disclosure make it heavy as a single block with no structural breaks.

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?

There is no output schema, but the description compensates by stating the return format (grade, score, weighted reasons). Combined with the scope exclusion and pricing terms, an agent has enough to decide whether to call it and what to expect back.

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?

Only one parameter exists, and its schema description already covers 100% of the semantics including normalization (scheme/path/port stripping, IDN punycode) and rejection rules (IP addresses, private names). The description adds nothing about the parameter, so baseline 3 applies.

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?

Names a specific resource and verb: 'Email authentication posture of a domain from DNS,' then enumerates the exact record types covered (MX/null MX, SPF mechanisms and all-qualifier, DMARC p/sp/pct/alignment, MTA-STS, TLS-RPT, BIMI). It does not explicitly differentiate itself from the sibling domain_dns, so an agent must infer that this is the analyzed posture view rather than raw record retrieval.

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 enumeration of checks and by explicit scope exclusions ('DKIM is not assessed because selectors cannot be enumerated'), which tells the agent what this tool will not answer. However, there is no explicit statement of when to choose this over domain_dns or email_verify, and no prerequisites are mentioned.

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