Skip to main content
Glama

Check email-domain health (MX / SPF / DMARC)

check_domain_health
Read-only

Check the DNS and deliverability health of an email domain: MX records, SPF, DMARC, and an overall health score. Useful for diagnosing why a domain bounces or for validating a sending domain.

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_domain_health"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that the result includes an aggregated health score and which record types are inspected, which is real value given there is no output schema. It omits cost/credit implications and lookup-failure behavior, which matters in a catalog that includes credit tools.

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 the resource and the checks performed, then the rationale. No filler, no repetition of the title's parenthetical beyond what is needed.

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?

With no output schema the description must convey what comes back, and it does (MX, SPF, DMARC, overall score). For a one-parameter read-only tool that is largely sufficient; the main gaps are whether the call consumes credits and what happens on unresolvable domains.

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 at 100% schema description coverage with an inline example ('example.com'), so the schema does the work. The description adds no format rules, no subdomain or IDN guidance, and no statement about normalization, so it sits at the baseline.

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 ('check') with a precise resource and scope: MX, SPF, DMARC and an overall health score for an email domain. It implicitly separates itself from the email-level siblings like verify_email by operating on the domain rather than a mailbox, though it never names an alternative.

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 states two concrete use cases — diagnosing why a domain bounces and validating a sending domain — which gives an agent a clear trigger. It stops short of exclusions or naming a sibling such as verify_email for per-address checks, so the routing decision is only implied.

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.