Skip to main content
Glama
eu-kyb-mcp

eu-kyb-mcp

by mastermabel

Check email domain

check_email_domain
Read-only

Validate an email domain before onboarding or invoicing by checking MX, SPF, DMARC, and disposable-provider signals via DNS without sending email or probing mailboxes.

Instructions

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.

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 (only the domain is used)
domainNoDomain (alternative to email)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value by clarifying the mechanism is DNS-only and that no mail is sent and no mailbox is probed. It stops short of disclosing lookup failure behavior, rate limits, or how a heuristic verdict is expressed.

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?

A single compact sentence that front-loads the method (DNS-based) and then the checks performed, followed by a short exclusion clause. Every phrase carries information; nothing is padded.

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 two-parameter, read-only lookup this is close to sufficient: the enumerated checks imply the shape of the result even without an output schema, and the non-side-effect clause sets expectations. The remaining gap is the unspecified requirement that one of the two optional inputs be provided, plus no hint about result structure beyond the list of checks.

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%, and both parameters carry their own descriptions including the note that only the domain portion of an email is used, so the schema does the heavy lifting. The description adds nothing about the fact that zero parameters are required or whether at least one of email/domain must be supplied, leaving that ambiguity unaddressed.

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?

Names a specific verb and resource ('DNS-based check of an email address's domain') and enumerates exactly what is examined: MX records, SPF, DMARC policy, and a disposable-provider heuristic. It does not explicitly contrast with the siblings (check_eu_vat, lookup_lei, request_verification_report), but those operate on entirely different identifiers, so misselection risk is low.

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 negative scoping sentence ('Does not send email or probe mailboxes') usefully rules out a common misconception about what this check does. However, there is no explicit statement of when to prefer this over the siblings, and no guidance on supplying email versus domain, which matters given both parameters are optional.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.