Skip to main content
Glama

Validate email addresses (DNS only)

validate_emails
Read-onlyIdempotent

Check email addresses without sending anything: syntax, MX records, disposable domains, role accounts, free providers and likely typos (gmial.com). Returns status valid/risky/invalid, a 0-100 score, reasons and a suggested correction. Up to 25 addresses per call.

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": {
      "emails": "<emails>"
    },
    "name": "validate_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailsYesEmail addresses to check (max 25).
check_dnsNoRun DNS/MX lookups (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so safety and network access are covered. The description usefully adds that nothing is sent, that DNS is optional, the batch ceiling, and the return vocabulary (valid/risky/invalid plus score, reasons, correction). It stops short of explaining what the results mean per status or that check_dns=false necessarily weakens MX/typo conclusions, which is the behavior an agent would most need to know.

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: the mechanism and the 'without sending anything' differentiator come first, the output contract second. 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?

With no output schema, the description correctly carries the return-value burden by naming the statuses, the 0-100 score and the reasons/correction fields. It is complete enough to call correctly, though a word on how check_dns=false changes the verdicts would close the last gap.

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 description coverage is 100%, so both properties are already documented with defaults and the 25-item cap. The description's 'up to 25 addresses per call' restates maxItems rather than adding meaning, and check_dns is not elaborated on beyond the schema's own 'Run DNS/MX lookups (default true)'. Baseline 3 applies.

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?

A specific verb (check) plus resource (email addresses) followed by an enumeration of exactly which signals are evaluated: syntax, MX records, disposable domains, role accounts, free providers, typo detection. The resource is distinct from every sibling listed (domains, PDFs, jobs, trades), so there is no routing ambiguity.

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?

'Check email addresses without sending anything' implies the appropriate context (non-invasive validation of a list) and the title's 'DNS only' further scope it, but there is no explicit when-to-use or when-not guidance and no named alternative for cases like actually verifying deliverability. Guidance is implied rather than stated.

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