Skip to main content
Glama

Verifly

by email.verifly

Verify a batch of email addresses

verify_batch

Synchronously verify a list of email addresses (best for up to a few hundred). Returns a per-address verdict for each email. For very large lists use the bulk async endpoint instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailsYesArray of email addresses to verify.
exclude_role_accountsNoFlag/exclude role accounts (info@, sales@, ...). Default false.
exclude_public_domainsNoFlag/exclude public domains (gmail.com, ...). Default false.

TDQS

A4.4/5.0
Behavior4/5

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

Without annotations, description discloses synchronous behavior and return of per-address verdicts. It does not cover error handling, rate limits, or prerequisites (e.g., credits), but main behavioral traits are adequately described.

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?

Two efficient sentences, front-loaded with key constraint ('synchronously', 'up to a few hundred'). No superfluous text. Every sentence earns its place.

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?

Given no output schema or annotations, the description adequately explains synchronous nature and return type. Missing details on error cases and prerequisites, but sufficient for basic use.

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 description adds no new parameter meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 clearly states 'Synchronously verify a list of email addresses' with a specific resource and verb. It contrasts with sibling tools like verify_email (single) and submit_bulk (async), establishing distinct purpose.

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?

Explicitly recommends 'best for up to a few hundred' and directs to 'bulk async endpoint' for larger lists, providing clear when-to-use and when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Verifly toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose. Overlaps like verify_batch vs submit_bulk are explicitly differentiated by synchronous vs asynchronous behavior. Extraction, cleaning, verification, and management tools are well-separated.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., register_account, verify_email, get_job_status). There is no mixing of conventions or vague verbs.

Tool Count5/5

15 tools cover the domain of email verification and account management without redundancy. Each tool fills a specific role—single verification, batch sync, bulk async, job polling, results retrieval, list cleaning, extraction, domain health, credit purchasing, and account management.

Completeness5/5

The tool set provides complete lifecycle coverage: account registration, usage tracking, credit purchase, email verification (single, batch, bulk with async), job management, list cleaning, email extraction, and domain health checks. No obvious gaps for the intended functionality.

Resources