Skip to main content
Glama

DNSFix

Write a DMARC record

build_dmarc_record
Read-onlyIdempotent

Writes a DMARC record for a domain as text, with where to add it and what each part does. It is never published: the domain owner adds it at their DNS host.

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

Input Schema

NameRequiredDescriptionDefault
domainYesA domain name, for example yourbusiness.com
policyNoDefault none (watch only)
report_emailNoOptional: where daily reports go
subdomain_policyNoOptional: policy for subdomains (sp=). Leave it out to use the main policy

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / subdomain_policy / description
      Added value: +"Optional: policy for subdomains (sp=). Leave it out to use the main policy"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The description adds the single most valuable fact the annotations cannot convey: the record is never published by the tool, resolving any confusion around "writes" versus readOnlyHint=true. It also discloses the return shape (text plus placement guidance and field explanations), though it does not cover validation behavior for invalid domains or policy combinations.

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 short sentences, the core action and its non-publishing constraint front-loaded, with zero filler. Every clause contributes either purpose or a behavioral fact.

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 four-parameter, non-destructive generator with no output schema, the description covers purpose, output form, and the publish-it-yourself boundary. Only minor gaps remain around validation and error behavior, which are unlikely to change how an agent invokes it.

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 coverage is 100% with enums documented inline (including the default of "none" and the sp= mapping for subdomain_policy), so the schema already carries the parameter burden. The description only alludes to parameters via "what each part does", adding no syntax or interaction detail 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?

"Writes a DMARC record for a domain as text" gives a specific verb plus resource and even the output form, which separates it from the check_* siblings that inspect existing records. It stops short of naming a sibling to route against, so the differentiation is implied rather than explicit.

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 line "the domain owner adds it at their DNS host" implies the generation-then-manual-publish workflow, but there is no explicit when-to-use-this-instead-of guidance and no stated prerequisites or exclusions relative to check_dmarc or scan_domain. Usage is inferable rather than stated.

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