Skip to main content
Glama

Easy Email Verification

Verify an email address

verify_email

Verify one email address with Easy Email Verification (syntax, domain, MX, mailbox, disposable, role and catch-all checks). Consumes one credit.

Read "result": valid, invalid or unknown. "unknown" means no reliable conclusion: treat it as neither valid nor invalid; catch-all addresses come back as unknown with reason "accept_all". "safe_to_send" is the overall recommendation; "disposable", "role", "free" and "accept_all" are signals for the user's own policy; "did_you_mean" suggests a typo fix. "success": true only means the request was processed.

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": "verify_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesEmail address to verify

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true and non-idempotent; the description adds the material facts the agent actually needs — that a credit is consumed, that "success": true only means the request was processed, and that "unknown"/"accept_all" must not be read as invalid. It does not mention failure modes, credit exhaustion, or rate limits.

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?

Front-loaded with the action and checks, then the credit cost, then the return-value semantics — a sensible priority order with no filler. It runs long for a one-parameter tool, but every clause maps to a field or outcome the agent would otherwise misread.

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 carries the full burden of explaining return values, and it does so field by field (result, safe_to_send, disposable, role, free, accept_all, did_you_mean, success). An agent can correctly interpret every plausible response without additional documentation.

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 there is only one parameter with its own description ("Email address to verify"), so the baseline of 3 applies. The description adds no format, normalization, or constraint detail beyond what the schema already states.

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?

"Verify one email address" is a specific verb+resource, and the parenthetical enumerates exactly which checks run (syntax, domain, MX, mailbox, disposable, role, catch-all). The word "one" plus "consumes one credit" cleanly separates it from the sibling verify_emails bulk tool.

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 establishes clear context: a single address, one credit per call, and the specific situation where "unknown" is a legitimate outcome rather than an error. It never explicitly names verify_emails as the alternative for batches or states when-not-to-use, so it falls short of a 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