Skip to main content
Glama
Systems Manager

Systems Manager

Dns Lookup

sm_network_dns_lookup
Read-onlyIdempotent

Performs DNS lookups to resolve a hostname into network records, helping verify DNS configuration and troubleshoot connectivity issues.

Instructions

Dns lookup (sm_network_operations). Operations for network analysis

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sm_network_dns_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoHost to ping or lookup

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no mention of DNS record types queried, resolver behavior, failure modes, or that a null host may default to local resolution.

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

Conciseness3/5

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

It is very short, but the second sentence ('Operations for network analysis') earns no place — it is generic category noise that does not help selection. The remaining content is essentially a restatement of the name plus a module reference.

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

Completeness2/5

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

The tool itself is simple and annotations are rich, but with no output schema the description should at least indicate what comes back (resolved addresses, records) and how a null host is handled. Neither is present, so an agent cannot predict the result.

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?

There is a single optional parameter with 100% schema description coverage, so the schema carries parameter documentation and the baseline of 3 applies. The description contributes no additional meaning about what 'Host to ping or lookup' accepts (hostname vs IP) or what happens when it is omitted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ('Dns lookup'), which is more specific than the title alone, but the trailing clause 'Operations for network analysis' is vague filler that does not tell an agent what a DNS lookup returns or how it differs from the sibling sm_network_ping_host — a distinction made only murkier by the schema text 'Host to ping or lookup'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: no statement about resolving a hostname versus verifying reachability (sm_network_ping_host), no prerequisite about the host argument, and no exclusions. An agent must infer selection from the tool name.

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