Skip to main content
Glama

dns_resolver_compare

Compare DNS answers from Cloudflare and Google over DNS-over-HTTPS to detect mismatches and investigate propagation, geo DNS, load balancing, or resolver policy differences.

Instructions

Compare public DNS answers from Cloudflare and Google over DNS-over-HTTPS.

Supports A, AAAA, MX, NS, TXT, CAA, and CNAME. A mismatch can reflect propagation, geo DNS, load balancing, or resolver policy.

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

Input Schema

NameRequiredDescriptionDefault
domainYes
record_typeNoA

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden: it discloses which upstream resolvers are used (Cloudflare and Google) and which record types are supported, which is real added context. However it says nothing about request volume, error behavior, or what the comparison result looks like, and there is no output schema to cover that gap.

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?

Two short paragraphs, front-loaded with the core comparison and followed by the supported set. The closing sentence about mismatch causes earns its place as interpretation guidance, though it could be tightened into one clause.

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?

For a two-parameter read tool this covers purpose and record-type scope adequately, but with no output schema the description should say what comes back (per-resolver answers, a match/mismatch verdict, TTLs) and does not. An agent knows what to send but not what to expect.

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 description coverage is 0%, so the description must compensate, and it does partially by enumerating the seven supported record types, which constrains the otherwise free-form record_type string. The domain parameter is left unexplained, presumably treated as self-evident, and the default of A is not restated.

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?

Names a specific verb and resource: compare public DNS answers from Cloudflare and Google over DNS-over-HTTPS. That distinguishes it from a plain dns_lookup, though the description never names an alternative explicitly, so differentiation is left implicit.

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 only implied by the note that a mismatch can reflect propagation, geo DNS, load balancing, or resolver policy, which hints at when the tool is useful (verifying propagation). There is no explicit when-to-use statement, no when-not-to-use, and no mention of dns_lookup as the single-resolver alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.