Skip to main content
Glama

Email Verification

email-verify
Read-only

Check whether an email address takes mail, or is disposable. Returns the status (valid, invalid, unknown when the mailbox is neither confirmed nor rejected, or do_not_mail for a throwaway provider) with a sub-status, whether it is a free mailbox, and the domain's mail servers and provider. Use before emailing an address you were given or found. To find an address from a person's name use emails. Cost: 1 credit, charged only when a call succeeds.

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

Input Schema

NameRequiredDescriptionDefault
emailYesEmail to verify.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, but the description adds genuinely non-obvious context: it explains the semantic difference between the `unknown` and `do_not_mail` statuses, the accompanying sub-status, free-mailbox flag and domain mail-server data, and states the cost model (1 credit, charged only on success). That last point is operational information an agent could not derive from structured fields. It stops short of describing error behavior or latency, so a 4 rather than a 5.

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?

Four compact sentences, front-loaded with the purpose before the return values, then the usage trigger, then the cost. Every sentence carries distinct information (capability, output semantics, routing, billing) with no restatement of the title or schema.

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?

No output schema exists, so the description is responsible for communicating return values, and it does so thoroughly by enumerating the four statuses plus the auxiliary fields returned. For a one-parameter read-only lookup, the remaining unknowns are minimal.

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 a single required parameter and schema description coverage is 100% ("Email to verify."), so the schema already carries the parameter's meaning. The description implies format expectations (a deliverable mailbox address) but adds no syntax, normalization or validation detail beyond that, which is the baseline case for full schema coverage.

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 ("Check whether an email address takes mail, or is disposable") and immediately enumerates the possible outcomes (valid, invalid, unknown, do_not_mail), which tells an agent exactly what decision this tool answers. It also distinguishes itself from the sibling `emails` tool by naming it as the lookup alternative rather than a verification one.

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?

Gives an explicit trigger ("Use before emailing an address you were given or found") and explicitly routes the adjacent use case elsewhere ("To find an address from a person's name use emails"). Both the when and the when-not are stated, so nothing is left to inference.

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.