Skip to main content
Glama

Verify an email address

verify_email
Destructive

Use this when the user wants to know whether an email address can receive mail, such as before writing to it or to avoid a bounce. Checks the one address without sending anything and answers its verdict: valid; invalid, which also covers addresses never to be written to, such as spam traps; risky, when its domain accepts mail for every address, so this one cannot be confirmed; or unknown, when no verdict could be had. Nothing is saved. $0.01 a verdict; an unknown verdict is free. A check takes a few seconds, 25 at most, and one that gets no verdict in time costs nothing and may be tried again. Verifications have their own limit, 60 a minute and 5,000 a day.

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
emailYesThe address to check, such as `ana.costa@fernway.co`. It is checked trimmed and in lower case.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses cost ($0.01 per verdict, free when unknown), latency (a few seconds, 25 max), retry semantics for timed-out checks, and a dedicated rate limit of 60/minute and 5,000/day. 'Nothing is saved' and 'without sending anything' describe the actual footprint, which is in mild tension with destructiveHint=true but is consistent with a credit-spending external call that persists no data.

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 use case, then verdicts, then cost/latency/limits — a sensible order with no filler. It is a dense single paragraph with long clauses, which slightly hurts scanability, but every sentence carries information.

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 return-value burden and does so by defining all four verdicts, including the practical meaning of 'invalid' and 'risky'. Cost, timing, retry and rate limits round out everything an agent needs to call it correctly.

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% for the single required parameter, and the schema already states trimming, lower-casing and the 320-character limit. The description adds only that exactly one address is checked, so the 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?

States a specific verb and resource — checking whether one email address can receive mail — and enumerates the four possible verdicts (valid, invalid, risky, unknown), including the special case that invalid covers spam traps. This is clearly distinct from the sibling verify_tracking_domain, which operates on a domain rather than a single address.

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?

The opening clause gives explicit when-to-use guidance: before writing to an address or to avoid a bounce. It does not name an alternative tool or state when not to use it (e.g. domain-level verification), but the triggering condition is unambiguous.

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