Skip to main content
Glama

List Dns Records V6

list_dns_records_v6
Read-onlyIdempotent

Retrieves local IPv6 DNS records from the Verizon CR1000A router, returning each entry as an index, name, and IP address.

Instructions

Local IPv6 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_v6"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.5/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 'Local' scope qualifier and the exact returned row fields, which is useful context beyond the annotations, but says nothing about ordering, pagination, or behavior when no 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.

Conciseness5/5

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

A single front-loaded clause with zero filler; the scope ('Local IPv6') comes first and the row structure second. Nothing could be removed without losing information.

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 zero-parameter read with an output schema and full annotation coverage, the description supplies what structured data does not: the local-only scope and the row field names. The one remaining gap is disambiguation from the sibling list_dns_records, which matters because that is the only real choice an agent faces here.

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 there is no parameter semantics to explain and the baseline is 4. The description correctly spends its words on the return shape instead of inventing input details.

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 a specific resource ('Local IPv6 DNS records') and its row shape ('{idx, name, ip}'), so an agent knows exactly what it gets back. It does not, however, distinguish itself from the sibling 'list_dns_records' (presumably IPv4 or aggregate), leaving the scope boundary implicit.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The only hint is the word 'Local' plus 'IPv6', which an agent must infer means 'use this instead of list_dns_records when you want IPv6-only local entries'.

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