Skip to main content
Glama

DNSFix

Check DMARC

check_dmarc
Read-onlyIdempotent

Reads a domain's DMARC record: the policy, every tag explained, and what to change.

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
domainYesA domain name, for example yourbusiness.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds real value by disclosing the shape of the response — the policy, per-tag explanations, and change recommendations — which tells the agent this is an interpretive tool, not a raw DNS dump. It stops short of saying what happens when no DMARC 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?

One sentence, front-loaded with the core action and followed by the three things returned. No filler, no restatement of the title, and every clause carries information the agent can act on.

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 rich annotations and no output schema, the description covers purpose, response contents, and remediation intent. The remaining gap — behavior on a domain with no DMARC record or on a subdomain — is minor but would materially affect an agent's retry and error-handling decisions.

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?

With a single required parameter and 100% schema description coverage, the schema already explains the domain argument with an example. The description adds nothing about accepted formats, subdomain handling, or normalization (e.g. whether a URL or a full email address is rejected), so the baseline of 3 applies.

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?

The description names a specific verb and resource ("Reads a domain's DMARC record") and enumerates the payload: policy, tag explanations, and remediation advice. It is clearly distinct from write-oriented siblings like build_dmarc_record, but it never explicitly contrasts itself with get_dmarc_summary, so sibling differentiation is only partial.

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

Usage Guidelines2/5

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

There is no explicit when-to-use statement, no prerequisites, and no exclusion of alternatives. An agent working against get_dmarc_summary, check_record, or check_dmarc-adjacent siblings must infer from the name alone which one to call for a live record read versus a cached summary.

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