Skip to main content
Glama

SPF, DMARC, MX & Disposable Domain Security Grader MCP

Grade Corporate Domain Email Security & Deliverability

grade_domain_email_security
Read-onlyIdempotent

Grades MX, SPF, DMARC, DKIM selectors, MTA-STS, TLS-RPT, BIMI, CAA, disposable domain status, and RDAP domain age with copy-paste DNS TXT fixes.

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

Input Schema

NameRequiredDescriptionDefault
domainYesCorporate domain name to inspect via live DNS-over-HTTPS and RDAP (e.g. stripe.com or cal.com)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description adds real value beyond that by disclosing the output's nature — 'copy-paste DNS TXT fixes' — telling the agent the result is actionable remediation text rather than a bare pass/fail. It stops short of explaining the grading scale or how missing/partial records are scored.

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?

A single front-loaded sentence with no filler; the enumeration is dense but each item names a concrete check the agent would want to know about. It is slightly list-heavy and could be tightened, but nothing is wasted.

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 one-parameter, read-only audit with no output schema, the description adequately conveys what is inspected and what the output looks like (TXT fixes). The notable gap is the absence of any hint about the grading scale or result structure for domains with absent records, which matters for interpreting 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?

There is a single parameter with 100% schema description coverage, and the description adds no syntax or format guidance beyond what the schema already states (domain name, live DNS-over-HTTPS and RDAP inspection). Baseline 3 is appropriate when the schema carries the parameter semantics.

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?

Uses a specific verb ('Grades') against a precisely enumerated resource set: MX, SPF, DMARC, DKIM selectors, MTA-STS, TLS-RPT, BIMI, CAA, disposable-domain status, and RDAP age. An agent immediately knows this is a domain email-security audit, not a generic DNS lookup.

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?

Scope is implied by 'Corporate Domain' and by the schema's '(e.g. stripe.com or cal.com)', so the intended input class is inferable. However, there is no explicit statement of when to reach for this tool, prerequisites (e.g. public DNS visibility), or what to do when a domain has no records — typical for a single-purpose tool with no siblings.

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.