Skip to main content
Glama

Email Verifier

email_verifier
Read-onlyIdempotent

Verify an email address with Hunter.io email verification. Checks deliverability, MX records, SMTP, and whether the address is disposable or webmail. Returns a status, result, and confidence score. Example: email_verifier({ email: "patrick@stripe.com" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "email": "patrick@stripe.com"
    },
    "name": "email_verifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesEmail address to verify, e.g. "patrick@stripe.com"
_apiKeyNoOptional, your own Hunter.io API key for higher limits; omit to use the shared Pipeworx key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"Optional — your own Hunter.io API key for higher limits; omit to use the shared Pipeworx key."New value: +"Optional, your own Hunter.io API key for higher limits; omit to use the shared Pipeworx key."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "email": "patrick@stripe.com"
      +  },
      +  {
      +    "email": "contact@github.com"
      +  }
      +]
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it names the third-party dependency (Hunter.io), enumerates the verification layers, and discloses the return shape (status, result, confidence score). It does not mention rate limits or what a partial/unverifiable result looks like, which is the remaining gap.

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 purpose, then the checks, then the return values, then a concrete call example — a logical progression with no filler. The example is slightly redundant with the schema's examples array, which keeps it from a 5.

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 two-parameter read-only verification tool with no output schema, the description supplies what an agent needs: what is checked, what comes back, and a worked example. Only minor omissions remain (behavior on invalid input, rate-limit consequences of omitting _apiKey), which the schema partially covers.

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 description coverage is 100% and both parameters are already documented, including the optional _apiKey and its rate-limit implication. The description restates the email parameter via an example invocation but adds no syntax, format, or validation detail beyond the schema, so the baseline of 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 ('Verify an email address') and immediately names the underlying provider (Hunter.io) plus the concrete checks performed (deliverability, MX, SMTP, disposable/webmail). This clearly distinguishes it from a discovery tool like email_finder, which locates addresses rather than validating them.

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?

The description implies the usage context — you already have an address and want to validate it — but never states when to use this versus email_finder or any other sibling, nor any preconditions such as needing a well-formed address or a valid API key. Guidance exists but is inferential rather than explicit.

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.