Skip to main content
Glama

OutboundAuth Deliverability

Check DMARC record

check_dmarc
Read-onlyIdempotent

Look up the live DMARC TXT record at _dmarc. and evaluate it: policy (none/quarantine/reject), aggregate reporting (rua). Returns a scored verdict with findings.

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": "check_dmarc"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain to check, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds genuine context beyond that: this performs a live DNS lookup (implying network dependency and possible lookup failure) and returns a scored verdict with findings rather than a raw record. It stops short of describing what happens when no record exists.

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?

Two tight sentences: the lookup and scope come first, the evaluated fields and return shape follow. No filler, no restatement of the title, and the enumerated policy values are the most decision-relevant detail placed early.

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 single-parameter read tool with full annotation coverage, this covers what is queried, what is evaluated, and roughly what comes back ('scored verdict with findings'), so absence of an output schema is not a problem. The one gap is the negative case — behavior when no DMARC record is published — which would help an agent interpret the result.

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 100%, so the baseline is 3, but the description earns an extra point by writing '_dmarc.<domain>', which clarifies that the agent supplies the bare domain (example.com) and the tool prepends the selector itself. That prevents a common misuse of passing '_dmarc.example.com'.

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 (look up and evaluate) plus the exact resource and its DNS location (_dmarc.<domain>), then enumerates what is inspected (policy values, rua). The DMARC resource is inherently distinct from the siblings check_dkim, check_spf, and check_email_auth, so an agent can disambiguate from the name and first clause alone.

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 resource named — an agent checking DMARC configuration will land here naturally — but the description never states when to prefer this over check_spf or check_email_auth, nor any prerequisites (e.g., checking SPF first or domain must be registered). 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