Skip to main content
Glama

LinkVet

Check an email address's domain can receive mail (DNS only)

check_email
Read-onlyIdempotent

Validate an email address without sending anything: RFC syntax, whether the domain exists, MX records (or implicit A record / null MX), SPF and DMARC presence, and flags for disposable, free-provider and role addresses (info@, support@). Proves the domain accepts mail, not that the mailbox exists.

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": "check_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYes

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?

Annotations already declare readOnly, idempotent and open-world, so the safety profile is covered. The description adds genuinely new behavioral context: nothing is sent, the check is DNS-only, and the result cannot confirm mailbox existence — an important expectation-setting caveat. It does not mention rate limits or latency/network failure behavior, so it is not exhaustive.

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?

Two sentences, front-loaded with the core action and the no-side-effect guarantee, followed by the check inventory and the key limitation. Every clause carries information; nothing is redundant or buried.

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 no output schema, the description carries the burden of explaining results, and it largely does by enumerating the signals returned (syntax, domain, MX, SPF, DMARC, address-type flags). What is missing is the shape of the response — whether these are booleans, nested objects, or explanatory strings — which leaves a small gap for an agent parsing 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 0% schema description coverage, but its meaning ('email' as the address to validate) is self-evident from the description's opening clause. No format, normalization, or error-handling guidance for malformed input is given, so it adds only marginal meaning beyond the schema.

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?

The description names a specific verb ('Validate an email address') and enumerates exactly what is checked: RFC syntax, domain existence, MX/A/null MX, SPF, DMARC, and disposable/free-provider/role flags. The sibling set (check_robots, check_url, read_page, verify_quote) makes it obvious this is the email-specific checker, with no ambiguity about scope.

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?

It gives a clear usage context ('without sending anything', 'DNS only') that distinguishes it from any mail-sending or mailbox-verification flow, and states the boundary condition ('Proves the domain accepts mail, not that the mailbox exists'). It stops short of naming an explicit alternative or a when-not-to-call rule, which keeps it below a 5.

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