Skip to main content
Glama

Paid public-data feeds (x402, 0.002 USD)

Email address pre-check in one call: syntax, MX records (or A fallback), likely deliverable, known disposable domain (em

email_check
Read-onlyIdempotent

Email address pre-check in one call: syntax, MX records (or A fallback), likely deliverable, known disposable domain (email=a@example.com). DNS-level only, never contacts the mailbox. For signup and lead-quality agents. Pay per call $0.002 USDC on Base via x402.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "email_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoaddress to check, e.g. a@example.com
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive and open-world access, so the bar is lower, yet the description adds real behavioral facts: the check is pure DNS with no mailbox contact, and each call costs $0.002 USDC on Base via x402. This pricing detail materially affects whether an agent should invoke it, which is exactly the kind of context annotations cannot express.

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

Conciseness4/5

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

Front-loaded with the capability and its sub-checks, then constraints, then pricing. Every clause carries information, though the parenthetical '(email=a@example.com)' partially duplicates the schema's example value and the title repeats the first sentence verbatim.

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?

With only two parameters, no output schema, and light annotations, the description covers what an agent needs: what is checked, what is deliberately not done, who it is for, and what it costs. The only gap is that 'likely deliverable' is not defined as a result shape, but that is minor given the absence of an output schema.

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 and the baseline is 3. The description earns one step above baseline by explaining the payment model behind x_payment (amount, asset, chain, x402 protocol), which gives an agent the cost context the schema's 'signed x402 payment' string does not.

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, then enumerates exactly what is checked: syntax, MX records with A fallback, likely deliverability, and known disposable domain. Nothing in the sibling list overlaps with this, and the scope ('DNS-level only') is unambiguous.

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?

Names a clear use context ('For signup and lead-quality agents') and a hard boundary ('never contacts the mailbox'), which tells an agent this is a pre-check rather than a verification. It stops short of explicit when-not guidance or exclusion cases, but no sibling alternative exists to route against.

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