Skip to main content
Glama

MailAuth Audit (Email Deliverability)

audit_mailauth_lite

Read-onlyIdempotent

FREE lite email deliverability audit of a domain (bare domain, e.g. example.com). Runs the same 12 SPF/DKIM/DMARC/MX checks as audit_mailauth but returns top-line results only: 0-100 score, A-F grade, spoofing/deliverability risk level, check counts, and the titles of the top gaps — the observed records and per-check evidence are capped. Use this to triage whether a domain needs the full audit_mailauth report, or call audit_mailauth directly for the complete evidence-backed scan.

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

Input Schema

NameRequiredDescriptionDefault
domainYesBare domain to audit, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only cover safety and idempotency; the description adds genuinely non-obvious behavior: the same 12 SPF/DKIM/DMARC/MX checks run as the full audit, but observed records and per-check evidence are capped, and the result is a score/grade/risk-bucket summary. The 'FREE' marker also signals a cost/quota distinction from the sibling, which annotations cannot express.

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, front-loaded with cost and scope ('FREE lite ... top-line results only'), then the routing alternative. No filler, and every clause carries distinct information about output shape, limits, or tool choice.

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, so the description carries that burden and does: it enumerates score, A-F grade, risk level, check counts, and gap titles, and warns that evidence is capped. For a single-parameter read-only tool, nothing an agent needs in order to call or interpret it is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so the single parameter is already documented, but the description still adds a meaningful constraint by insisting on a bare domain format with an example, excluding URLs or email addresses. That meaning would otherwise have to be inferred from the schema's example alone.

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 a specific verb and resource — a free lite email deliverability audit of a domain — and immediately narrows scope ('top-line results only') in contrast to the named sibling audit_mailauth. An agent can tell exactly which of the two tools produces which artifact without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit decision rule: use this to triage whether a domain needs the full report, or call audit_mailauth directly for the complete evidence-backed scan. It also constrains the input form ('bare domain, e.g. example.com'), which is a usage prerequisite, not just a parameter note.

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.