Skip to main content
Glama

Managed Nerds

check_email_security

Read-onlyIdempotent

Free email security check for any domain (also accepts an email or website address): whether scammers can send email that looks like it came from it, and why its mail might land in spam. Checks SPF, DKIM, DMARC, the mail provider and MTA-STS from public DNS, grades it (good, needs work, at risk) and gives the exact records to add. Sends no email and needs no contact details; the domain and result are kept 90 days, nothing about who asked. 20 checks an hour per address.

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": {
      "domain": "<domain>"
    },
    "name": "check_email_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesexample.com, you@example.com or https://example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds real value on top: no email is sent, no contact details required, retention is 90 days, requester identity is not stored, and there is a 20-per-hour rate limit. Those are exactly the operational facts an agent needs to set expectations and avoid over-calling.

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 dense but well-ordered block: purpose, accepted inputs, what is checked, what is returned, then privacy and limits. Every clause carries information an agent would otherwise have to guess, and nothing is repeated.

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

Completeness5/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 carries the burden of describing results and does so concretely (grade categories plus exact records to add). Input flexibility, privacy, retention, and rate limits are all covered, leaving no material gap for a one-parameter read-only 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% and the single parameter already documents that an email or URL form is acceptable, so the description's 'also accepts an email or website address' restates rather than extends the schema. Baseline 3 applies; no normalization or edge-case detail (e.g., how an email input is resolved to a domain) is added.

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 — 'Free email security check for any domain' — and immediately enumerates the exact surface examined (SPF, DKIM, DMARC, mail provider, MTA-STS) plus the output shape (grade plus records to add). An agent reading only this can tell it is an anti-spoofing/deliverability audit, not a general domain lookup like check_domain.

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?

Usage is implied rather than stated: it is clear you call this when you want an email-security posture for a domain, and the accepted input forms are spelled out. However, there is no explicit when-not guidance and no named alternative among the siblings (e.g., check_domain or check_ai_readiness), so routing between overlapping 'check_*' tools is left to inference.

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