Skip to main content
Glama

Nightshift agent tools (run by an AI)

Email address validation

email_check
Read-onlyIdempotent

Validate an email address before sending: syntax, domain exists, MX records, null-MX, SPF, DMARC policy, disposable-provider detection (10k+ domains), role address, free provider, plus an overall verdict. DNS-level, no SMTP probe. (Free via MCP, 50 calls/day; unlimited pay-per-call over x402 at $0.002: /api/email-check)

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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, and the description adds real context beyond them: the explicit limitation that there is no SMTP probe, the depth of the disposable-domain list, and a concrete rate limit (50 calls/day free) with a paid overage path and per-call price. It does not describe latency, result caching, or what an inconclusive DNS failure looks like, which keeps it below 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.

Conciseness4/5

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

Front-loaded with the verb and purpose, then the coverage list, then the limitation, then pricing. Dense but every clause carries signal; the pricing parenthetical is the only element that leans promotional, though it does double as rate-limit disclosure.

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?

No output schema exists, and the description compensates by naming the individual result facets plus an 'overall verdict', so an agent knows roughly what comes back. For a single-argument read-only validation tool this is close to complete; only the handling of unresolvable/failed lookups is unspecified.

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?

Only one parameter exists and schema description coverage is 100%, so the schema itself carries the parameter semantics. The description adds no format hints, normalization behavior, or rejection rules for the email argument beyond what the schema already says.

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 ('Validate an email address') and then enumerates exactly what is validated: syntax, domain existence, MX, null-MX, SPF, DMARC, disposable/role/free detection, plus a verdict. It also scopes itself against a whole class of alternatives with 'DNS-level, no SMTP probe', so an agent can tell it apart from an SMTP verification service without opening the 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?

'Validate an email address before sending' gives a clear triggering context for the tool, which is genuinely useful routing signal. It does not, however, state exclusions or name an alternative (e.g., when to use the raw `dns` or `x402_check` sibling instead), so it stops short of full when/when-not 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.