Skip to main content
Glama

Email check

email_check

Email verification. Check ONE email address before sending to it: shape, live MX records, disposable domain, role account. The mailbox itself is not probed. $0.001 per call, USDC on Base.

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": {
      "email": "<email>"
    },
    "name": "email_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesexactly one email address
paymentNoa signed x402 payment (the same base64 payload you would put in the PAYMENT-SIGNATURE header). Pass it here and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the negative space ("The mailbox itself is not probed"), which prevents over-trusting the result, and states pricing ($0.001 per call, USDC on Base). It omits rate limits, caching, and latency, keeping it from a 5.

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 action, then the checks, then the caveat and price. No filler; every clause adds information an agent would act on.

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 single-purpose check with no output schema, the definition covers what is tested, what is not tested, and what it costs. The one remaining gap is that the shape of the returned verdict (fields, pass/fail semantics) is never hinted at.

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 the schema already documents both parameters, including the x402 payment mechanics in detail. The description adds only the pricing context and reinforces the single-address constraint, so the 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 and resource ("Email verification. Check ONE email address") and enumerates the exact checks performed: shape, live MX records, disposable domain, role account. The explicit "ONE" scope also distinguishes it from the bulk sibling without naming it.

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?

"Check ONE email address before sending to it" gives clear timing and intent: pre-send validation. It does not explicitly point to email_verify_bulk for multi-address work or name other alternatives, so it stops short of full routing 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