Skip to main content
Glama

email_batch

Read-only

Check email syntax, domain routing and disposable-address signals in one batch. 0.0006 USDC per address, minimum 0.001 USDC per request; up to 100 addresses.

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": "email_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailsYesBetween 1 and 100 addresses. Billed at 0.0006 USDC per address with a 0.001 USDC minimum charge.
smtp_checkNoAsk for an optional SMTP probe. Off by default, heavily throttled, one attempt per target and never retried. Without it the verdict of a routable address stays "unknown".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false and idempotentHint=false. The description adds genuinely new context the annotations don't carry: the exact cost model (0.0006 USDC per address, 0.001 USDC minimum per request) and the hard cap of 100 addresses, which matter for batching decisions. It stops short of explaining the non-idempotency or the throttling of the optional SMTP probe, but the pricing disclosure is substantive.

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 tightly packed sentences with the capability stated first and the cost/limit constraints second. No filler, no repetition beyond the unavoidable cost restatement.

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 batch tool with rich annotations and full schema coverage, the description covers purpose, cost and size limits. The one gap is return shape: with no output schema, the description never says what a verdict looks like or how results are keyed per address, leaving the agent to infer it from the smtp_check note.

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% and both parameters are fully documented in the schema, including the SMTP probe's throttling and 'unknown' verdict behavior. The description only restates the price and address cap already present in the emails parameter description, adding no new parameter 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?

States a specific verb ('Check') with the exact resource and the three signal classes it evaluates (syntax, domain routing, disposable-address), plus the batch scope. An agent immediately knows this is bulk email validation, which none of the siblings (domain_profile, ip_reputation, speech_to_text, technology_stack) do.

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?

Usage is only implied: 'in one batch' and 'up to 100 addresses' signals bulk validation, but the description never says when to prefer this over a single-address check or any alternative, and gives no exclusions or prerequisites. Adequate inference, no explicit guidance.

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