Skip to main content
Glama

DNSFix

Check DNS propagation

check_propagation
Read-onlyIdempotent

Asks six big public DNS services (US, Europe and Asia) for the same record and says whether a change has reached them, and how long older copies last.

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": {
      "name": "<name>"
    },
    "name": "check_propagation"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesA DNS name, for example yourbusiness.com or _dmarc.yourbusiness.com
typeNoRecord type (default A)
expectNoOptional: the new value you expect, or part of it

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?

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuine behavior beyond that: the check spans six resolvers in three regions and reports TTL-style remaining lifetime of stale answers, which the agent could not infer from the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with no filler, front-loading the mechanism before the outcome. The parenthetical region list makes it slightly dense but every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does its part by describing what the result conveys (propagation status plus stale-copy lifetime), but it omits anything about resolver failures, timeouts, or result shape. Adequate rather than complete for a network-dependent checker.

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 description coverage is 100%, with per-parameter descriptions and an enum for record type, so the schema carries parameter meaning. The description adds nothing about name/type/expect semantics beyond confirming that one record is queried; baseline 3 applies.

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 concrete mechanism (querying six public resolvers across US, Europe and Asia for one record) and a concrete outcome (whether a change reached them, plus how long stale copies persist). That mechanism cleanly separates it from the single-lookup sibling lookup_dns without needing to name it.

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 phrase 'whether a change has reached them' implicitly scopes usage to just-after-editing-a-record checks versus a plain lookup, and the regional resolver framing signals when this beats a simple query. It stops short of explicit when-not guidance or naming lookup_dns as the lighter alternative.

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