Skip to main content
Glama

UAI x402 Security Tools

dns-email-security-audit

DNS email security audit — SPF, DMARC, DKIM, BIMI, and MTA-STS check for domain spoofing and deliverability risk. Agent-friendly dns email security screen at micropayment pricing. (REST equivalent: POST /api/v1/dns-email-security-audit, $0.0045)

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-security-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain to audit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations carry only a title, so the description must supply behavior. It usefully discloses that this is a paid micropayment call ($0.0045) with a REST equivalent endpoint, and 'screen'/'check' implies a non-destructive read. It does not state whether lookups are live DNS queries, how long they take, fail on missing records, or what the result format looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first clause is well front-loaded, but 'Agent-friendly dns email security screen at micropayment pricing' restates the name and purpose in marketing language, adding only the price signal. The REST/pricing parenthetical is genuinely useful; the rest could be trimmed.

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?

For a simple one-parameter tool this is largely adequate on inputs, but with no output schema the description should say something about what the audit returns (per-record pass/fail, risk findings, scores). That gap leaves an agent unsure what to expect from the call.

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 ('Domain to audit'), so the baseline is 3. The description adds no format constraints (e.g., whether a bare domain vs URL vs subdomain is expected) beyond the schema.

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?

States a specific verb (audit/check) and resource (DNS email security), and enumerates exactly what is examined: SPF, DMARC, DKIM, BIMI, MTA-STS. It is clear what the tool does, though it does not explicitly distinguish itself from the near-adjacent sibling 'email-vendor-risk-summary' or 'ssl-certificate-audit'.

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 through the stated goals ('domain spoofing and deliverability risk'), which tells an agent the screening scenario but not when to prefer this over sibling security audits or when it is unnecessary. No explicit exclusions or alternatives 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