Skip to main content
Glama

AgentSupply

Check email domain deliverability

check_email_domain
Read-only

DNS-based check of an email address's domain: MX records, SPF, DMARC policy and a disposable-provider heuristic. Does not send email or probe mailboxes. Live tool – free during the pilot, rate-limited.

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

Input Schema

NameRequiredDescriptionDefault
emailNoEmail address to check (only the domain is used).
domainNoDomain to check (alternative to email).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real context on top: that it performs live network lookups, that it is rate-limited, that it is free during the pilot, and that one signal is only a 'heuristic' (warning that disposable verdicts may be approximate). It falls short of 5 only because it does not explain what a returned verdict or confidence looks like.

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 dense sentences, front-loaded with the mechanism and scope, then constraints. Nothing is redundant with the title or annotations.

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?

No output schema exists, so the description should convey what comes back (per-record booleans? a single deliverable verdict?), and it does not. It also omits that both parameters are optional yet one is practically needed, leaving a real gap for a zero-required-parameter tool.

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?

Schema coverage is 100%, so the schema already documents both parameters, and the description only restates that only the domain portion is used. It adds no tie-breaking rule for what happens if both email and domain are supplied, nor notes that at least one is effectively required.

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?

Names a specific verb+resource ('DNS-based check of an email address's domain') and enumerates the exact signals examined: MX, SPF, DMARC and a disposable-provider heuristic. An agent can immediately distinguish this from check_eu_vat, lookup_lei or get_request_status 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?

'Does not send email or probe mailboxes' usefully bounds what the tool will not do, and 'free during the pilot, rate-limited' signals cost/throughput constraints. However, it never states when to pick this over a sibling or what prerequisite the caller needs, so selection guidance is only implied.

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