Skip to main content
Glama

Email Validator API - syntax, MX, disposable, typos (bulk 500)

email_validator
Read-onlyIdempotent

Check up to 500 e-mail addresses per call: syntax, duplicates, domain typos with the fixed address (gmial.com -> gmail.com), live DNS MX lookup (domain exists and accepts mail), disposable and role addresses. Status ok / risky / bad with the reason. Never sends mail to anyone. Free: 25 calls/day per IP. Paid: $0.003 per call via x402 at https://radarbg.com/x402/email-validator.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "emails": [
        "info@github.com",
        "test@gmial.com",
        "x@mailinator.com"
      ]
    },
    "name": "email_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoOne address, e.g. info@example.com
emailsNoOr a list of up to 500

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld, and the description adds genuinely non-obvious behavior on top: rate limits (25/day per IP), cost ($0.003/call via x402 with a URL), the output taxonomy (ok / risky / bad plus a reason), and the explicit safety guarantee that it 'never sends mail to anyone'. The MX lookup detail also explains why openWorldHint is set, which is useful for an agent reasoning about latency and external dependencies.

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?

Three tight sentences, front-loaded with what gets checked, then the status vocabulary, then the safety and pricing constraints. Every clause carries information an agent needs — no restated name or filler.

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?

For a read-only validator with no output schema, this is close to complete: inputs, statuses, reasons, limits, cost and side-effect profile are all covered. The residual gap is edge behavior — what happens above 500 addresses, and whether 'email' and 'emails' can be combined — which is minor for this tool's complexity.

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 both parameters are already documented, including the 'up to 500' cap on the emails array, so the description adds essentially no syntax or format meaning beyond the schema. It also leaves the mutual relationship between the singular 'email' and the 'emails' array (either/or, precedence, or whether both may be supplied) unresolved — the schema labels them 'One address' / 'Or a list', and the description does not clarify further.

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 opens with a specific verb+resource ('Check up to 500 e-mail addresses per call') and enumerates exactly what is checked: syntax, duplicates, domain typos, live DNS MX, disposable and role addresses. That level of specificity makes it clearly distinct from siblings like email_auth or domain_intel without needing to be told.

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 gives clear operating context: bulk batches of up to 500 per call, a free 25 calls/day IP quota, and a paid x402 path, which tells an agent when the tool is practical and what happens at scale. It stops short of an explicit 'use this rather than X' routing statement against the email-related siblings, so it lands at 4 rather than 5.

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