Skip to main content
Glama

email_auth

Read-only

Check SPF, DMARC, MX and common DKIM selectors for up to 5 domains via DNS-over-HTTPS. Reports policy strength, common misconfigs (multiple SPF, SPF lookup limit, +all, p=none), a simple grade and recommendations. Mailbox existence is never probed. Not a deliverability or safety guarantee. Price: 0.01 USDC per call (x402, Base).

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": {
      "domains": "<domains>"
    },
    "name": "email_auth"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesDomains, or email addresses (only the domain is used)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations declare readOnlyHint and openWorldHint, and the description goes well beyond them by disclosing the cost model (0.01 USDC per call via x402 on Base), the exact lookup mechanism (DNS-over-HTTPS), the checks performed, and negative guarantees about what is not done. Output content (policy strength, misconfigs, grade, recommendations) is summarized so the agent knows what comes back 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 definition is front-loaded: the checks performed come first, followed by what is reported, then scope caveats, then price. It is dense with no filler, though the terse list-style clauses make it slightly harder to scan than a cleanly separated sentence structure would.

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?

For a single-parameter tool with no output schema, the description covers mechanism, inputs, what is returned, known failure patterns it flags, cost, and explicit limitations. An agent has everything needed to decide whether to call it and to interpret the result without additional documentation.

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% and the schema already documents that email addresses are accepted with only the domain used, and caps items at 5. The description's 'up to 5 domains' restates maxItems rather than adding new meaning, so the schema is doing the heavy lifting and baseline 3 applies.

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?

The description names a specific verb and resource set — checking SPF, DMARC, MX and common DKIM selectors for up to 5 domains — plus the transport mechanism (DNS-over-HTTPS). No sibling tool covers email authentication, and 'email_auth' alone could not tell an agent this checks DNS records rather than validating credentials, so the clarification is substantive.

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?

It gives clear scope boundaries: mailbox existence is never probed, and results are not a deliverability or safety guarantee, which tells the agent when this tool's output is and isn't sufficient. It stops short of naming an alternative for the excluded cases (e.g., mailbox verification), so it is not a full when/when-not/alternative routing.

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