Skip to main content
Glama

BRAINIAC Email & Domain Intelligence

Analyze a DMARC policy

email-domain_dmarc-policy-analyze

Read the _dmarc TXT record and report p and pct. A missing record, a failed lookup, and p=none are separate results. No aggregate report is sent. Price $0.03 USDC. POST /api/v1/email-domain/dmarc-policy-analyze. Unpaid calls return 402 and do not run.

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-domain_dmarc-policy-analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does useful work: it says missing records, failed lookups, and p=none are separate results, clarifies that no aggregate report is sent, and explains payment behavior including 402 responses. It still does not describe rate limits or the complete response shape, but it covers key side-effect and access behavior.

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?

The definition is short and front-loaded: core behavior comes first, then result distinctions, then payment and endpoint details. Every sentence adds operational meaning without repetition.

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 simple one-parameter read-only lookup, the description is largely complete: it covers the record source, reported fields, lookup outcomes, non-sending behavior, price, endpoint, and unpaid-call handling. It leaves minor gaps around domain input format and exact response details, but is otherwise sufficient.

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?

The schema has 0% description coverage for the single domain parameter, so the description must compensate. It implies that domain is used to locate the _dmarc TXT record, but it does not specify whether the value should be a bare registrable domain, a hostname, or another format.

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 states a specific verb and resource: read the _dmarc TXT record and report p and pct. It clearly distinguishes this DMARC-policy lookup from general domain checks by naming the exact record type and reported fields.

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?

The intended use is implied by the narrow DMARC-record scope, but the description does not explicitly say when to choose this versus SPF, DKIM, MX, or other sibling checks. It gives no exclusions or routing guidance.

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