Skip to main content
Glama

Check a signup email

check_email
Read-onlyIdempotent

Checks one email address the way a signup form would: invalid syntax, disposable/throwaway domain, domain that cannot receive mail (no MX), likely typo with a suggested fix (e.g. gmial.com -> gmail.com), privacy relay (Apple Hide My Email, Firefox Relay: allowed, they reach a real inbox) and role addresses. Returns a verdict (allow, suggest, warn, block) with reasons.

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
emailYesThe email address to check, e.g. jane@gmial.com

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 cover the safety profile (readOnly, non-destructive, idempotent, open-world), so the description's job is additive context. It does that well: privacy relay domains are intentionally allowed because they reach a real inbox, and typos yield a suggested fix. It doesn't address external-lookup failure modes or latency from the open-world DNS calls, which keeps it off 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?

One dense sentence front-loads the verb and the check categories, followed by the verdict enumeration. Every clause earns its place, though the inline parenthetical on privacy relays and the mid-list typo example make it slightly list-like rather than scannable.

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 one-parameter, read-only validation tool with no output schema, the description supplies the input expectation, the checks performed, and the four verdict values needed to interpret results. It leaves unclear how the 'reasons' field is shaped and what an agent should do on a 'suggest' verdict.

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% with a single string parameter, so the baseline is 3. The description adds meaning beyond the schema by confirming it validates one address and that typo detection returns a suggested correction, reinforced by the gmial.com -> gmail.com example.

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 (checks) and resource (one email address) scoped as 'the way a signup form would', then enumerates the exact check categories (syntax, disposable domain, no MX, typo suggestion, privacy relay, role addresses) and the verdict levels. An agent can distinguish it from check_domains and same_inbox without opening any schema.

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?

The 'signup form' framing and the enumerated checks imply the signup-validation context, but the description never explicitly says when to use this versus check_domains or how_to_block, nor does it state exclusions such as bulk list validation. Usage is inferred rather than directed.

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