Skip to main content
Glama

Verify one email address

verify_email

Verify one email address and return the full result: status (valid, invalid, unknown, temporary_unavailable), deliverable and reachable flags, catch_all, disposable, free and role_account signals, confidence, a reason code (such as mailbox_not_found, catch_all, greylisted or probe_blocked), the mail provider and MX hosts, the mail server's SMTP reply code as evidence, a did_you_mean typo suggestion, plus the same recommended action decide_send gives. Costs 1 credit; repeats within 72 hours come from cache for free, a malformed address is rejected without charge, and a result we can't resolve is free. Use decide_send instead when you only need the send decision.

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 email address to check, for example jane@example.com.
strictnessNoHow cautious the recommended action is. default: catch-all domains get review. aggressive: catch-all domains get send_with_caution. strict: as default, and role addresses such as info@ or sales@ also get review. Defaults to default.
force_refreshNoSkip the 72-hour cache and verify again now. Costs 1 credit even when a cached result exists. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, openWorldHint=true; the description adds the entire billing and caching model (credit cost, 72-hour free cache, no charge on malformed input or unresolvable results) and notes the SMTP reply is returned as evidence. That is substantial beyond annotations. It stops short of describing rate limits, latency, or what happens on transient failures other than the 'temporary_unavailable' status token.

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?

Purpose and the alternative-tool routing are front-loaded, and the long field enumeration is justified because no output schema exists. The middle field list is a dense run-on of comma-separated signals that could be trimmed or bulleted, but there is no genuinely wasted sentence.

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 takes on the full burden of describing return values and does so thoroughly, including status vocabulary, reason codes, and evidence fields. Combined with the cost/caching rules and the decide_send routing, an agent has enough to invoke it correctly and interpret the response.

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%, so the enum values and defaults for strictness and force_refresh are already fully documented. The description only echoes credit implications that duplicate the schema's own force_refresh wording, adding no new syntax or format meaning; 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?

The description opens with a specific verb+resource ('Verify one email address') and then enumerates the exact result payload (status, deliverable/reachable, catch_all, disposable, role_account, confidence, reason codes, provider/MX, SMTP code, typo suggestion). It explicitly contrasts scope with the sibling 'decide_send' ('the same recommended action decide_send gives'), so an agent can distinguish the two without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names an alternative and the condition that selects it: 'Use decide_send instead when you only need the send decision.' It also gives cost-driven usage context (1 credit, 72-hour cache is free, malformed addresses and unresolvable results are free), which tells the agent when calling is cheap versus wasteful.

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