Skip to main content
Glama

NovaPixel LexGrid

email_deliverability_audit

Resolves full DNS tree to audit SPF syntax (recursive 10 lookup limit check), DMARC policy, DKIM selectors, BIMI, MTA-STS and TLS-RPT records.

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. First observed

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose one genuinely useful trait — that SPF evaluation follows the DNS tree and enforces the recursive 10-lookup limit — but says nothing about read-only/safe nature, resolution timeouts, rate limits, or how failures (NXDOMAIN, missing records) are represented. For a tool with zero annotation coverage this is a meaningful gap.

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 sentence, front-loaded with the mechanism and followed by the audited record types. Every clause carries information and nothing is redundant.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description is the only source of truth, yet it never indicates what an audit returns (per-record status, issues found, pass/fail) or how partial failures are reported. It adequately covers scope but not outcome or operational expectations for a multi-record audit 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 description coverage is 100%, so both 'domain' and 'selector' are already documented, including the default probe list for selectors. The description only adds an oblique hint via 'DKIM selectors' (plural) and does not explain selector syntax or behavior beyond what the schema already states, so baseline 3 is correct.

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?

The description opens with a specific verb and mechanism ('Resolves full DNS tree to audit') and then enumerates the exact record families covered: SPF, DMARC, DKIM, BIMI, MTA-STS, TLS-RPT. That enumeration makes it unmistakable versus the sibling tools (RDAP registration data, port scanning, TLS/HTTP inspection) without needing to name 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 only implied — an agent can infer this is the tool for email-authentication/DNS posture auditing, but the description never states when to choose it, any prerequisites (publicly resolvable domain, live DNS), or when another tool would be more appropriate. No exclusions or alternative routing 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