Skip to main content
Glama

List Ipv6 Pinholes

list_ipv6_pinholes
Read-onlyIdempotent

Lists configured IPv6 pinhole (inbound firewall) rules on the router so you can review which inbound IPv6 connections are allowed.

Instructions

Configured IPv6 pinhole (inbound firewall) rules.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the clarifying detail that pinholes are inbound firewall rules, which is real conceptual context. It stops short of stating whether the list is scoped to a device, whether results are paginated, or whether disabled rules are included — though the output schema can carry 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.

Conciseness4/5

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

A single short fragment with zero wasted words — nothing to trim. The trade-off is that brevity here reflects under-specification rather than disciplined editing, and the front-loaded resource name is at least the right thing to lead with.

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?

For a zero-parameter read-only tool with an output schema and full annotation coverage, the description is close to sufficient — the agent mainly needs to know what a pinhole is, which it supplies. What is missing is confirmation that this is a listing operation and any hint of scope or filtering. Adequate but with clear gaps.

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 nothing for the description to disambiguate beyond the schema. Baseline of 4 applies; no parameter semantics are missing.

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 identifies the resource precisely — 'Configured IPv6 pinhole (inbound firewall) rules' — and the parenthetical usefully glosses 'pinhole' as an inbound firewall rule. However it is a noun phrase with no verb, so the listing action is only inferred from the tool name and title rather than stated. It also does not distinguish this from siblings such as list_port_forwards or list_dns_records_v6.

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 guidance on when to call this tool, no prerequisites, and no mention of alternatives. The description does not tell an agent whether this returns configured rules versus active connections, or how it relates to the IPv4 port-forwarding sibling. Usage is left entirely to inference from the name.

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