Skip to main content
Glama

zato crypto data

Email address check: syntax, MX, SPF, DMARC, role and disposable domain - no mailbox contact

email_check
Read-only

Plausibility of an email address: syntax, MX, SPF, DMARC, role and disposable domain. No mailbox contact. Price: $0.002 USDC per call (x402, 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
emailYesemail address to check

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?

Annotations already cover read-only and open-world behavior, but the description adds two facts they do not: the check makes no mailbox contact (no SMTP probe, so no side effects on recipients) and each call costs $0.002 USDC via x402 on Base. The payment requirement is materially important for agent planning and is nowhere in the structured fields. It does not describe the result shape, but a 4 reflects solid added context.

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?

Two compact sentences with zero padding, and the enumerated check list is front-loaded ahead of the pricing note. The only mild friction is the noun-phrase opener 'Plausibility of an email address' rather than a direct statement of what the tool does.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool with no output schema, the definition covers scope, safety, and cost well. What is missing is any indication of what comes back — whether each check returns an individual pass/fail, an aggregate score, or a boolean — which an agent needs in order to interpret the result.

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?

There is a single required parameter with 100% schema coverage, so the schema already carries the burden. The description does not restate or enrich the parameter beyond implying the input is an address to be evaluated for plausibility, which is the baseline expectation when schema coverage is complete.

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 names the resource (an email address) and enumerates exactly what is evaluated: syntax, MX, SPF, DMARC, role and disposable domain. 'Plausibility' plus 'No mailbox contact' makes the scope and its limits unambiguous, and the email focus is clearly distinct from the DNS, sanctions, wallet, and payment siblings.

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?

'No mailbox contact' functions as an implied exclusion, telling the agent this is a non-invasive check rather than an inbox-verification probe, so it is appropriate for pre-registration screening. However, there is no explicit when-to-use statement, no prerequisites, and no named alternative for cases where a stronger verification is needed.

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