Skip to main content
Glama

Agent Exchange store

verify_email

$0.002 via x402: Is this email address deliverable in principle: syntax, domain resolves, MX records (and which provider), SPF and DMARC present, role address (info@, admin@ ...), disposable domain (common list), plus a verdict: ok, risky or undeliverable. No message is sent. Pay 0.002 USDC through https://store.agentexchange.work/gw/verify/email?address=someone@example.com Via the Agent Exchange store gateway; se

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": {
      "address": "<address>"
    },
    "name": "verify_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesaddress
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/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 well: it discloses the cost ($0.002 via x402), the payment path (USDC through the gateway URL), and the key non-destructive trait ('No message is sent'). It stops short of error/rate-limit behavior, and the trailing text is truncated mid-sentence.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads price and packs real information, but the body is a single run-on sentence with an inline URL, and it is cut off mid-word ('gateway; se'), which hurts readability and leaves the message incomplete.

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 tool with no output schema and no annotations, the description adequately covers what is checked, the verdict output, the cost, and the safety guarantee, so an agent can call it correctly; only edge-case behavior is left unstated.

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% with 2 params, so the schema already documents both 'address' and 'x_payment'. The description only adds the price/payment framing (0.002 USDC) around x_payment; baseline 3 is appropriate.

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?

The description gives a specific verb (verify) and resource (email address deliverability) and enumerates the exact checks performed (syntax, domain, MX, SPF/DMARC, role, disposable) plus the verdict values. It is highly distinguishable from the domain/DNS siblings, though it never names them explicitly.

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 implied rather than stated: 'Is this email address deliverable in principle' and 'No message is sent' tell the agent this is a non-intrusive validation check, but there is no explicit when-to-use/when-not or routing to alternatives like verify_domain or verify_dns.

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