Skip to main content
Glama
Sign In

InfraNest

by io.infranest
OverviewDiscussionsAdmin

Check one DNS name

check_dns_name
Read-onlyIdempotent

Everything about one hostname, e.g. mail.example.com: the zone it belongs to, its records in InfraNest, whether live DNS answers the same, the zone's delegation, and any change made directly at the DNS provider that nobody has decided on. Start here for "why does this name not resolve" or "where does this point".

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_dns_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe hostname, e.g. mail.example.com.
organization_idNoThe organization to read. Leave it out when the token reaches only one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior1/5

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

The annotations declare openWorldHint=false, but the description says the tool reports 'whether live DNS answers the same', which implies an external live DNS lookup. That is an annotation contradiction; despite otherwise useful disclosure of returned data, the rule requires a 1 when the description contradicts annotations.

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?

It is two sentences, front-loaded with the scope and then the use cases. Every clause maps to a returned data category or a selection scenario, with 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 does well by enumerating the main categories of information returned. It does not specify response structure or error behavior, but it is otherwise complete enough for an agent to call it correctly.

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. The description reinforces the hostname example but adds no extra semantics for organization_id or default behavior, so the 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?

The description states a specific operation on a specific resource: checking one hostname and returning its zone, records, live DNS comparison, delegation, and provider-side changes. The scope word 'one' helps distinguish it from list/search siblings such as search_dns and list_dns_records.

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?

It gives clear diagnostic entry-point guidance: use it for 'why does this name not resolve' and 'where does this point'. It does not explicitly mention when not to use it or name the alternative sibling tools.

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

All InfraNest 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