Skip to main content
Glama
RoscoNL

intodns-mcp

by RoscoNL
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_email_test

Read-onlyIdempotent

Check the status of an email test session using its test ID. Returns 'pending' until the test email arrives, then provides full SPF, DKIM, DMARC, headers, and spam-score analysis.

Instructions

Read-only status read for an email-test session. Returns 'pending' until a test email arrives at the unique address returned by create_email_test, then full SPF/DKIM/DMARC/headers/spam-score result once processed. Requires testId from create_email_test. Use after sending a test message to that address; for explicit processing of just-arrived mail use poll_email_test instead. Idempotent GET, no auth.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
testIdYesEmail test ID returned by create_email_test

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.10.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only and idempotence, but the description adds valuable behavioral context: 'pending' until delivery, then full SPF/DKIM/DMARC/headers/spam-score results, and no-auth access. This goes beyond the structured metadata without contradicting it.

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?

Four sentences, each earning its place: purpose, behavior, dependency, usage timing, alternative, and idempotence/auth status. Front-loaded with the core action and no redundancy.

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?

Despite having no output schema, the description sufficiently explains both possible return states ('pending' and full results) and the required input origin. Given the tool's simple read-only nature, this is complete and actionable.

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 single parameter `testId` is already well-documented in the schema. The description reinforces its origin from create_email_test but adds no significant new syntax or formatting detail.

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 uses a specific verb ('status read') and names the exact resource ('email-test session'). It clearly distinguishes itself from sibling tools by contrasting with poll_email_test and referencing create_email_test.

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 explicitly states when to use the tool: after sending a test message to the unique address. It also provides a direct alternative ('use poll_email_test instead') and identifies the required prerequisite (`testId` from create_email_test).

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

Deploy Server

Other Tools