Skip to main content
Glama

List Dns Records

list_dns_records
Read-onlyIdempotent

Retrieves local IPv4 DNS records from a Verizon CR1000A router, returning each record's index, hostname, and IP address for inspection.

Instructions

Local IPv4 DNS records as {idx, name, ip} rows.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is fully covered. The description adds the scoping detail that records are 'local' and IPv4-only, plus the row shape, but says nothing about ordering, pagination, or failure behavior when no local records exist.

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?

A single front-loaded sentence with no filler, which is proportionate for a parameterless read. The only blemish is the doubled-backtick markup around the row shape, which is formatting noise rather than content.

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?

With an output schema documenting return values and annotations covering safety, the description only needs to establish scope and routing, and it does the former. It is thin on the latter: an agent choosing among the IPv4/IPv6 pairing and other list_* tools gets no explicit guidance.

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?

The tool takes zero parameters, so the schema carries no semantics the description needs to compensate for. Nothing is missing on this dimension.

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?

The description names the specific resource (local IPv4 DNS records) and the shape of each row ({idx, name, ip}), which distinguishes it from the sibling list_dns_records_v6 by stating IPv4 explicitly. It stops short of an explicit verb like 'list', relying on the name/title for that, but the resource is unambiguous.

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 statement of when to call this versus list_dns_records_v6 or other listing tools, and no prerequisites or exclusions. The only routing signal is the incidental word 'IPv4', which an agent must infer implies the v6 sibling handles the other case.

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