Skip to main content
Glama

Email address verification (syntax, MX, risk flags)

email_verify
Read-only

Checks an email address without sending mail: syntax rules (IDN domains in punycode and Unicode), MX records by preference, null MX (RFC 7505), implicit A/AAAA fallback, NXDOMAIN, SPF and DMARC policy, disposable, role, free-webmail and +tag flags, mail provider from MX hosts, and typo suggestions for popular domains. Returns a verdict and 0-100 score with reasons. Mailbox existence is not confirmed. Sources: Cloudflare DNS over HTTPS, disposable-email-domains (CC0). Price: $0.003 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

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": {
      "email": "<email>"
    },
    "name": "email_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesEmail address to check, up to 512 characters (addresses over 254 octets are reported as invalid). A mailto: link (its ?query and #fragment dropped) or a Name <address> header form is unwrapped first. Inputs without an @, quoted local parts, IP-literal domains and mailto links with several addresses are rejected with 400 and not charged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description still adds substantial context: the exact cost and payment rail ($0.003 per successful call, USDC via x402 v2), the explicit no-charge cases for failures and no-match results, upstream data sources, and the caveat that mailbox existence is not confirmed. Its only gap is that it does not describe rate limits or timeout behavior for live DNS lookups.

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 purpose is front-loaded and the long enumeration of checks is dense but each item is a distinct capability an agent would want. Pricing and caveats are packed into trailing sentences, which is slightly heavy but nothing is filler.

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?

With no output schema, the description still explains the return contract (verdict plus 0-100 score with reasons), the non-guarantee on mailbox existence, the sources, and the billing semantics. That covers everything needed to decide, call, and interpret results for a single-parameter read-only tool.

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 parameter at 100% schema coverage, so the schema already documents the 512-character limit, mailto/header unwrapping, and the 400 rejection cases. The description largely restates that ground rather than adding new meaning, 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 opens with a precise verb and resource ('Checks an email address without sending mail') and enumerates exactly which signals are evaluated (syntax/IDN, MX, null MX, SPF/DMARC, disposable/role/free-webmail tags, typo suggestions) plus the output shape (verdict and 0-100 score). It never names a sibling, and it overlaps with domain_email_auth by mentioning SPF/DMARC, so an agent gets no explicit signal about which of the two to pick.

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 rather than stated: 'without sending mail' and 'Mailbox existence is not confirmed' tell the agent what it will not get, which is a useful exclusion. However, no when-to-use condition or alternative (e.g., domain_email_auth for domain-level auth) is offered, leaving routing to inference.

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