Skip to main content
Glama

Email verify

email_verify

Check up to 100 email addresses in one call: shape, MX records read live, disposable domains and role accounts, with a verdict per address. Domain deliverability, not a mailbox probe. $0.009 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
emailsYescomma-separated addresses, up to 100
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the price ($0.009 per call), the accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), the mandatory terms-then-pay handshake, that MX records are read live, and the limit of what is actually tested (no mailbox probe). Cost and auth flow are the two things an agent most needs before a paid mutation-style call, and both are spelled out.

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 dense sentences, front-loaded with what is checked and bounded by what it is not, then price, then the call sequence. No filler, no restatement of the tool name, and the payment protocol is ordered in the same sequence the agent must execute it.

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?

There is no output schema, so the description must stand in for return-shape guidance, and 'a verdict per address' is the weakest part — the possible verdict values and whether bad addresses fail the whole batch or return per-address errors are left unstated. Everything else an agent needs (scope, price, payment handshake, batch limit) is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented, giving a baseline of 3. The description adds genuine meaning beyond the schema by explaining that `payment` is optional on the first call (unpaid terms fetch) and that supplying it completes the purchase inside the same call, which the schema text does not convey.

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 email addresses), the batch bound (up to 100), and exactly what is checked: shape, live MX records, disposable domains, role accounts. The line 'Domain deliverability, not a mailbox probe' draws a clean boundary that lets an agent separate this from mailbox-level verification siblings without opening a schema.

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?

Usage is clearly framed: batch use up to 100 addresses, domain-level verification only, and a concrete two-step invocation protocol (call without `payment` for terms, sign, call again with `payment`). What's missing is explicit routing to named siblings such as email_check or leads_verify_domains, so the agent must infer the alternative from the 'not a mailbox probe' phrase.

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