Skip to main content
Glama

Verify a batch of email addresses

verify_batch
Read-only

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

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": {
      "emails": "<emails>"
    },
    "name": "verify_batch"
  }
}

Input 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false), so the description only needs to add context. It does add that execution is synchronous and that results are broken out per address, but it says nothing about credit consumption, latency, or failure handling — notable for a tool sitting beside get_credits and buy_credits.

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?

Three short sentences, front-loaded with the core action and scale limit, then the return shape, then the fallback routing. Nothing is repeated from the title and no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 should describe what a "verdict" contains — possible values, confidence, or reason codes — and it does not. Cost and sync-timeout behavior are also absent, leaving real gaps for a tool whose results drive downstream cleaning decisions.

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%, so emails, exclude_role_accounts, and exclude_public_domains are all documented in the schema with defaults. The description adds nothing beyond that on parameters and never mentions the two exclusion flags, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Synchronously verify a list of email addresses" states a specific verb and resource, and the 100-address cap plus per-address return makes the batch scope explicit. It does not name verify_email as the single-address counterpart, so the boundary with that sibling is only inferable from the word "list".

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 description gives a clear operating envelope (up to 100 addresses, synchronous) and an explicit routing rule: very large lists should go to the bulk async endpoint. The alternative is described by role rather than by tool name, so the agent must map "bulk async endpoint" to submit_bulk itself, and no guidance is given for the 1-address case.

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.