Skip to main content
Glama

email_security

Audit a domain or email address for SPF, DMARC, DKIM, BIMI, MTA-STS, TLS-RPT, and CAA misconfigurations, returning a score, grade, issues, and actionable fixes.

Instructions

Audit a domain's email security: SPF, DMARC, DKIM, BIMI, MTA-STS, TLS-RPT and CAA.

Accepts a domain or an email address. Queries DNS TXT/MX/CAA records, checks common DKIM selectors, fetches the MTA-STS policy, and returns a score, grade, issues and concrete recommendations.

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

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it does substantial work: it states the underlying actions (queries TXT/MX/CAA records, tests common DKIM selectors, fetches the MTA-STS policy) and the return shape (score, grade, issues, recommendations). It never says whether the call is read-only or has side effects, nor mentions latency or rate limits, which matters for a tool that fans out into many DNS queries.

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 sentences, zero filler. The scope sentence comes first, followed by the mechanism-and-output sentence, which is exactly the right front-loading for a scan tool.

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?

For a single-parameter, no-output-schema tool, the definition covers the essential triangle: what is inspected, what input forms are valid, and what the result contains (score, grade, issues, recommendations). Nothing an agent needs in order to choose and call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the schema only exposes an unexplained "domain" string, so the description must compensate, and it does: it clarifies that either a bare domain or a full email address is acceptable. The only friction is that the required parameter is named 'domain' while email addresses are also valid, a mismatch the description does not reconcile.

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 opens with a specific verb and resource ("Audit a domain's email security") and enumerates the exact protocols covered: SPF, DMARC, DKIM, BIMI, MTA-STS, TLS-RPT and CAA. That is far more precise than a generic 'check email security' phrasing, though it never names or contrasts against a plausible sibling such as email_intel, leaving the agent to infer the boundary.

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 only implied: an agent can infer this is the tool for auditing domain email-auth posture, and the note that it accepts a domain or an email address widens the applicable input case. There is no explicit when-to-use framing, no when-not-to-use, and no pointer to which alternative tool handles related but different lookups.

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