Skip to main content
Glama

dns_lookup

Read-onlyIdempotent

Resolve a DNS name and time the lookup, with support for A, AAAA, CNAME, MX, NS, and TXT records. Query an alternate resolver to check whether local DNS is causing connectivity issues.

Instructions

Look up one DNS name and time the lookup. record_type: A, AAAA, CNAME, MX, NS or TXT. server: optional resolver to ask instead of the system one (e.g. 1.1.1.1), useful to tell whether the local DNS is the problem.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
serverNo
record_typeNoA

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 behavior, so the baseline requirement is low. The description adds two useful facts: the call is timed, and an alternate resolver can be targeted for diagnosis. It omits how failures, such as NXDOMAIN versus timeout, are surfaced, but the output schema carries return details.

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 short block that front-loads the core action, then documents the two optional parameters in order. Every sentence, including the diagnostic hint, adds information rather than repeating the schema.

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 simple three-parameter read-only lookup with a full annotation set and an output schema, the description covers purpose, record types, and resolver selection. The remaining gap is name format and error semantics, which is a minor omission given that structured fields cover the rest.

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 has to carry parameter meaning, and largely does: it enumerates all six record_type values and explains server's default behavior and diagnostic purpose with an example. The required 'name' parameter is never described, so there is no explicit statement that it is an FQDN.

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?

States a specific verb and resource ('Look up one DNS name') plus an extra role ('time the lookup'), which makes the scope clear. It is naturally distinct from check_port/ping/traceroute, but it does not explicitly contrast itself with them.

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?

The clause 'useful to tell whether the local DNS is the problem' gives a real when-to-use reason for the server parameter, which is better than nothing. However, there is no guidance on when to prefer this over ping or traceroute, and no stated exclusions or prerequisites.

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

Deploy Server

Other Tools