Skip to main content
Glama

DNSFix

Check a record before you paste it

check_record
Read-onlyIdempotent

Tests a DNS record someone gave you (from a chatbot, a DNS host or a web person) against the domain's live records before it is published: SPF lookups and dropped senders, DMARC that would block your own mail, DKIM keys, MX moves, CNAME clashes. Says safe, careful or stop. Never publishes anything.

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>",
      "record": "<record>"
    },
    "name": "check_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoOptional: the host or name field, if it was given separately
domainYesA domain name, for example yourbusiness.com
recordYesThe record as you were given it, for example: TXT _dmarc "v=DMARC1; p=reject"

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 cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), and the description reinforces it with "Never publishes anything" while adding genuine new information: the three-tier verdict output (safe, careful, stop). It omits detail on what the verdict includes or how findings are reported, so there is still some room.

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 long, information-dense sentence establishing what is tested and why, followed by a two-word outcome summary and a safety disclaimer. No filler and the scope constraint is front-loaded.

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 three-parameter analytical tool with no output schema, the description covers purpose, inputs' provenance, the shape of the result (safe/careful/stop) and the non-mutating guarantee. It stops short of explaining whether a detailed per-check diagnosis accompanies the verdict, which would matter for a tool with no output schema.

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% and each of the three parameters is documented in the schema, so the schema carries the load. The description adds only the framing that `record` is used verbatim as received, and never mentions the optional `host` parameter, so it does not meaningfully exceed the baseline.

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?

Uses a specific verb ("Tests") on a specific resource (a DNS record) against the domain's live records, and enumerates the failure modes it covers (SPF lookups and dropped senders, DMARC blocking, DKIM keys, MX moves, CNAME clashes), which separates it from the single-record-type siblings such as check_spf or check_dmarc.

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

Usage Guidelines4/5

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

The trigger is explicit and concrete: use it on a record "someone gave you (from a chatbot, a DNS host or a web person)" before publication. It does not name alternatives or state when a narrower sibling (check_spf, check_dkim) would be the better pick, so it falls short of a 5.

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