dns-doctor

Get Email Test Result

get_email_test

Read-onlyIdempotent

Use this after start_email_test, once the user says they sent the email. Returns status pending | received | expired | error. pending means the message has not arrived (or is still being checked): ask the user to send it if they have not, then call again. received carries result: the sending IP and reverse DNS, STARTTLS, SPF, every DKIM signature, DMARC with alignment and the disposition the policy implies, message format, links, domain age, blocklist and malware-feed status, and a score out of 10 with every deduction itemized, plus advice. With scoring_version 2 the score has one decimal and is 10 only when nothing was deducted and not_scored lists no check marked blocks_ten; an older test (scoring_version 1) keeps its original score. A version 2 result also carries sender_requirements (Gmail's, Yahoo's, Microsoft Outlook's and Apple's published sender rules against what this message showed, not a compliance verdict) and result.estimates.providers: for gmail, yahoo, microsoft and apple, accepted_pct (whether it takes the message at all) and inbox_pct (inbox rather than spam once accepted; null when there is no estimate), each with its basis. Relay them as estimates, never as a promise of delivery. A 'temperror' is a lookup that did not complete, NOT a failure, and is never scored. Present any record in result.dmarc.fix verbatim and never compose one; when it is null and result.dmarc.fix_withheld is set (for example a domain on Automatic DMARC), relay that reason instead. SPF is diagnose-only and DKIM keys come from the sending provider. The deduction coded ai_read and ai_assessment, when present, come from an automated read of the redacted message: attribute them as such (ai_read costs at most 0.5 points) and never present either as a spam score. Read-only.

Input Schema

Name	Required	Description	Default
`test_id`	Yes	The test_id start_email_test returned — not the test address. Tests started without an account are kept 24 hours; an unknown id is refused as not found.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / test_id / description

Previous value: -"The test_id start_email_test returned — not the test address. Tests are kept 7 days; an unknown id is refused as not found."New value: +"The test_id start_email_test returned — not the test address. Tests started without an account are kept 24 hours; an unknown id is refused as not found."

AddedOct 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, but the description adds substantial context beyond that: status meanings, scoring-version differences, temperror semantics, DMARC fix handling, SPF diagnose-only scope, and AI-derived deduction attribution. There is no contradiction with annotations, and the extra behavioral detail is unusually rich.

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 description is front-loaded with the correct usage and status semantics, and nearly every sentence carries operational value. It is dense and lengthy for a single paragraph, and some returned-field enumeration overlaps with the output schema, but the length is largely justified by the tool's behavioral complexity.

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?

Given the complex result semantics, the presence of an output schema, and the annotations, the description covers the critical gaps an agent would otherwise miss: how to interpret pending, how to treat temperror, how to relay provider estimates, and how to handle DMARC fix text. It is complete for correct invocation and interpretation.

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 coverage is 100%, and the schema already explains that test_id is the value returned by start_email_test, not the test address, including retention and not-found behavior. The description does not add further parameter-specific detail, so the baseline 3 is appropriate.

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 clearly states the specific operation: retrieving an email test result after start_email_test. It distinguishes the polling/retrieval step from the sibling start_email_test and names the returned status values, so an agent can identify the tool's role immediately.

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?

It gives explicit timing: use after start_email_test once the user says they sent the email. It also explains the pending loop — ask the user to send it if needed, then call again — which is precisely the kind of procedural guidance an agent needs for a polling tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All dns-doctor tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.