Skip to main content
Glama

email_check

Validate an email address for RFC syntax, domain MX/A records, disposable domains, and role accounts to assess deliverability without an SMTP probe.

Instructions

Email address check: RFC syntax, domain MX/A records (deliverability signal, no SMTP probe), disposable-domain and role-account flags. Costs 0.001 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesemail

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and discharges most of it: it discloses the explicit limitation ('no SMTP probe'), the pricing model (0.001 USDC on Base per successful call), the x402 payment protocol, and the failure mode when no payment key is supplied (a 402 challenge rather than a validation result). What is missing is any statement of rate limits, latency, or the shape of a successful response, which matters because there is no output schema.

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, no waste, and correctly front-loaded: the capabilities come first, then the commercial/payment mechanics. Every clause carries information an agent needs — the check list, the SMTP exclusion, the price, and the 402 behavior.

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 single-parameter validation tool with no annotations and no output schema, the description covers what is checked and the payment gate, which is the bulk of what an agent needs before calling. The remaining gap is the return shape — an agent must infer the result fields (valid flag, disposable/role flags, MX findings) from the enumerated checks rather than being told them.

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 one parameter with 100% schema description coverage, so the baseline of 3 applies — the schema already documents that 'email' is the input. The description adds mild value by making clear the address itself is what gets parsed for RFC syntax and domain resolution, but it offers no format constraints or normalization behavior beyond the schema.

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?

Names a specific verb+resource ('Email address check') and enumerates exactly what is verified: RFC syntax, domain MX/A records, disposable-domain and role-account flags. An agent can distinguish it from sibling validators (iban, gtin_validate, eori_validate) purely from the text without opening the schema.

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 by the subject matter — validating an email address before relying on it — but there is no explicit when-to-use statement, no when-not condition, and no named alternative. The parenthetical 'no SMTP probe' hints at a boundary versus a deeper verification tool, but does not tell the agent what to use when a real SMTP probe is required.

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