Skip to main content
Glama

OutboundAuth Deliverability

Full email authentication check

check_email_auth
Read-onlyIdempotent

Run the complete deliverability authentication check for a domain: SPF, DMARC, DKIM (probes common selectors), and MX records. Returns a scored verdict per area plus an overall summary.

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain to check, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by noting DKIM relies on probing 'common selectors' (flagging the partial-coverage caveat) and that output is a scored verdict per area plus an overall summary. It stops short of mentioning lookup rate limits, failure/timeout behavior, or what a 'no record found' result looks like, so it sits at 3.

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, zero filler, with the scope and the covered record types front-loaded before the return-value note. Every clause carries information an agent can act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only tool with full annotation coverage, this is close to sufficient: it names the checks performed and summarizes the return shape even though no output schema exists. The remaining gaps are edge-case handling (missing DKIM selector, DNS failure) rather than anything blocking correct invocation.

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 required parameter with 100% schema description coverage including an example, so the schema already does the work. The description adds no further semantics such as whether a bare hostname or a full email/URL is tolerated, so the 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?

The description gives a specific verb and resource ('Run the complete deliverability authentication check for a domain') and enumerates the four areas covered: SPF, DMARC, DKIM, and MX. The word 'complete' plus the multi-area enumeration implicitly distinguishes it from the per-record siblings check_spf/check_dmarc/check_dkim, though it never names them explicitly.

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 'complete ... check' versus the granular siblings, so an agent can infer this is the one-shot aggregate call. However, there is no explicit statement of when to prefer it over the individual checkers, nor any exclusion or prerequisite guidance.

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