Skip to main content
Glama

SentriSend Email Validation

Validate email address

validate_email
Read-only

Validate one email address with SentriSend's existing validation API. Checks syntax, disposable-domain status, and DNS/MX records; it does not check whether a specific mailbox exists. Uses the connected SentriSend API key and the same monthly request allowance as a direct validation call. It never sends email.

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

Input Schema

NameRequiredDescriptionDefault
emailYesOne email address to validate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, and closed-world, and the description adds genuinely new behavior: it consumes the connected API key, draws down the same monthly request allowance as a direct validation call, and never sends email — real cost/auth/side-effect context. The only friction is that DNS/MX lookups imply external network traffic while openWorldHint is false, a mild tension rather than a stated contradiction.

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?

Four tight sentences with the verb and resource front-loaded and the negative scope immediately after the positive one. 'SentriSend's existing validation API' is slightly vague filler, but nothing else is wasted.

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?

With no output schema, the description never indicates what comes back — a boolean, a status enum, or per-check flags — nor how a disposable/DNS failure is surfaced. For a single-parameter validation tool the input side is fully covered, but the result shape is left entirely to inference.

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 the single parameter already carries its own description, so the baseline is 3. The description adds only the singular constraint ('one email address', i.e. no batching), which is useful but minimal.

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 and resource ('Validate one email address') and then enumerates exactly which signals are checked (syntax, disposable-domain status, DNS/MX) and which are not (mailbox existence). An agent knows precisely what the tool does without opening the schema.

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?

The scope note 'one email address' and the explicit exclusion of mailbox-existence checking make the intended use case clear, so an agent will not reach for it as a deliverability guarantee. No sibling tools exist, so no alternative routing is needed, but the description also never states a positive 'use this when…' trigger.

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.