Skip to main content
Glama

DNS and email security check

dns_email_check
Read-onlyIdempotent

DNS + email security audit via DNS-over-HTTPS: A/AAAA/MX/NS/CAA, SPF, DKIM (common or given selectors), DMARC policy, grade A-F and concrete 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": "dns_email_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
dkim_selectorsNocomma-separated

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/openWorld, so the description is free to add mechanism: DNS-over-HTTPS lookups, DKIM probing with 'common or given selectors', and a grade A-F plus concrete fixes output. That tells the agent what comes back and how the check behaves, beyond what the annotations declare.

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?

One dense, front-loaded sentence with the mechanism first and the deliverable (grade + fixes) last. It is packed with enumeration but every listed item earns its place by defining audit scope.

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?

With no output schema, the description still specifies the return shape (record-by-record findings, letter grade, concrete fixes) and that queries go over DoH. Minor gaps remain around rate limits and whether partial failures still yield a grade.

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 50% and 'domain' has no schema description; the description implies the input is a domain to audit and adds that DKIM selectors default to 'common' when not supplied, which the schema's 'comma-separated' note does not convey. That default behavior is genuine added meaning.

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 names a specific verb+resource ('DNS + email security audit') and enumerates exactly what is checked: A/AAAA/MX/NS/CAA, SPF, DKIM, DMARC. This clearly separates it from record-returning siblings like get_dns, though it never explicitly names them.

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 by the audit/grade framing ('grade A-F and concrete fixes') versus get_dns's raw record retrieval, but the description never states when to pick this over get_dns or apply_dns_template. No exclusions or prerequisites are given.

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