Skip to main content
Glama

LexGrid NetSec, Deliverability & RDAP

email_deliverability_audit

Read-onlyIdempotent

[Live DNS query audit. Read-only, non-destructive, side-effect free]. Resolves authoritative DNS records to audit SPF syntax (including recursive 10-lookup RFC limit check), DMARC policy enforcement, DKIM public key selectors, BIMI SVG certificates, MTA-STS mail security, and TLS-RPT reporting records. Usage: Use this tool to evaluate email authentication and anti-spoofing posture for a domain. For general web HTTPS certificate inspection, use 'tls_http_inspector' instead. Returns: JSON object with { domain: string, spf: { valid: boolean, lookupsCount: number, record: string }, dmarc: { valid: boolean, policy: string, record: string }, dkim: { found: boolean, selector: string }, bimi: object, mtaSts: object, deliverabilityScore: number, recommendations: string[] }.

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_deliverability_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesTarget domain name (e.g. novapixel.it)
selectorNoOptional DKIM selector (default probes google, default, k1, mail)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / selector / description
      Previous value: -"Optional DKIM selector (default: probes google, default, k1, mail)"New value: +"Optional DKIM selector (default probes google, default, k1, mail)"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds real context beyond them: it confirms the data comes from live authoritative DNS queries, and it discloses the recursive 10-lookup RFC limit check performed on SPF. It also reveals implicit behavior not in the schema at a high level (BIMI/MTA-STS/TLS-RPT probing). It stops short of stating rate limits, timeouts, or behavior for non-resolving domains, which keeps it below a 5.

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?

Front-loaded with a bracketed safety tag, then purpose, then usage, then returns — a clean scannable structure with no filler sentences. The record-type enumeration is dense but each item earns its place by telling the agent what will be probed; the description is on the long side for a two-parameter tool.

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 compensates by spelling out the return object's top-level keys (spf, dmarc, dkim, bimi, mtaSts, deliverabilityScore, recommendations), which is exactly what an agent needs to plan downstream use. Remaining gaps are minor edge-case behavior (invalid/non-existent domains, partial DNS failure, response latency).

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 description coverage is 100%, including the default DKIM selector probes, so the schema already carries parameter meaning. The description does not discuss the 'domain' or 'selector' parameters or clarify selector override behavior, so it adds nothing beyond the schema. Baseline 3 applies when the schema does the work.

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+resource ('resolves authoritative DNS records to audit SPF... DMARC... DKIM... BIMI... MTA-STS... TLS-RPT') and enumerates the exact record families checked. It explicitly distinguishes itself from the sibling 'tls_http_inspector', so an agent can pick between them without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Usage:' line gives a direct when-to-use rule ('evaluate email authentication and anti-spoofing posture for a domain') and names the alternative for the adjacent use case ('For general web HTTPS certificate inspection, use tls_http_inspector instead'). Both the selection and the exclusion are explicit.

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