Skip to main content
Glama
Sign In

HTTPfy network & DNS tools

by io.httpfy
OverviewDiscussionsAdmin

DNS propagation check

dns_propagation_check
Read-onlyIdempotent

Query a domain on about 40 public resolvers in different regions and report which ones return which answers, to see whether a DNS change has propagated.

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_name": "<domain_name>"
    },
    "name": "dns_propagation_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
query_typeNoCheck Type. Default: NameserverNameserver
domain_nameYesDomain Name (Enter Domain Name)

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 declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds genuinely useful context beyond that: the fan-out scale (~40 resolvers), the geographic spread, and that results are per-resolver answer comparisons rather than a single verdict. It omits runtime/latency expectations and any rate-limit notes.

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?

A single sentence with the scope and mechanism front-loaded and the purpose stated last; every clause carries information and there is no filler.

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?

With no output schema, the description correctly carries the return-value burden by explaining that results are per-resolver answers. Complete enough to call correctly, though it does not set expectations for how long a 40-resolver sweep takes or whether results are cached.

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%, so both parameters are already documented in the schema, including the query_type enum and its default. The description adds no extra meaning about how 'Nameserver' vs 'IP' changes the output, so 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 specific verb (query), resource (domain), mechanism (about 40 public resolvers in different regions), and goal (see whether a DNS change has propagated). That combination distinguishes it from dns_lookup, which is a single-resolver lookup, without needing to name the sibling.

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 stated purpose ('to see whether a DNS change has propagated') gives a clear triggering context: use this after making a DNS change. It does not, however, state when not to use it or explicitly point to dns_lookup for a plain single-resolver query.

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

All HTTPfy network & DNS tools toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources