Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

check_email_advanced

check_email_advanced
Read-onlyIdempotent

Validate an email address and assess deliverability, fraud, spam-trap, disposable-domain, and DNS authentication signals to decide whether it is safe to accept or contact.

Instructions

Retrieves advanced information about an email address (spfDetails, dmarcDetails, createdAt, updatedAt, state, message, success, valid, disposable, smtpScore, overallScore, firstName, generic, common, dnsValid, honeypot, deliverability, frequentComplainer, spamTrapScore, catchAll, timedOut, suspect, recentAbuse, fraudScore, suggestedDomain, leaked, sanitizedEmail, identityData, domainAge, firstSeen, riskyTld, spfRecord, dmarcRecord, mxRecords, aRecords) Args: email: the email to 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": "check_email_advanced"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety and repeatability are covered structurally. The description adds some behavioral signal by revealing the breadth of the check (honeypot, spamTrapScore, catchAll, timedOut suggest a live deliverability probe that may be slow or credit-consuming), but it never states cost, latency, or that timedOut means the result is partial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The core sentence is overloaded by a raw, unordered dump of roughly 35 field names that mixes result fields, error fields (message, success, timedOut), and derived scores with no grouping or priority. The trailing 'Args:' block is a schema restatement that does not earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the field enumeration is the only return-value documentation, and it is unusable without semantics: nothing defines ranges or meanings for fraudScore, smtpScore, deliverability, or state, nor what a timedOut or catchAll result implies. For a tool producing this many signals, the description leaves the agent unable to interpret its own output.

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 description coverage is 0%, so the description must carry the load, and it does only minimally: 'the email to check' restates the parameter name without adding format, normalization, or validation expectations. With a single unambiguous required string, little is lost, but nothing is added either.

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?

The description states a concrete verb and resource: it retrieves advanced information about an email address, and the parenthetical field list makes clear this is a validation/risk-scoring lookup. It does not, however, distinguish itself from the sibling check_email_start, so an agent cannot tell from the text alone which of the two email tools to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no conditions, and no mention of check_email_start as the lighter alternative. The only implicit signal is the word 'advanced' in the name, which the agent must interpret on its own.

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