Skip to main content
Glama

List Port Forwards

list_port_forwards
Read-onlyIdempotent

Lists configured port-forwarding rules from a Verizon CR1000A router, including user and UPnP rules; optionally includes firmware-reserved read-only rules.

Instructions

Configured port-forwarding rules (user rules and UPnP rules).

Firmware-reserved read-only rules are only counted unless include_readonly is true.

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

Input Schema

NameRequiredDescriptionDefault
include_readonlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds a genuinely useful behavioral detail — that firmware-reserved read-only rules are excluded by default — but the phrasing 'only counted unless' is ambiguous about whether they are omitted from results or merely omitted from a count, which undercuts the added value.

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?

Two short sentences with no filler, and the main scope statement is front-loaded before the parameter caveat. The awkward line break and the compressed 'only counted unless' clause cost some readability but not much space.

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?

An output schema exists, so return values need no explanation, and the read-only nature is covered by annotations. What remains missing is any usage context and a clear statement of the default filter's effect, which for a single-parameter listing tool is a noticeable but modest gap.

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?

The single parameter has 0% schema description coverage, so the description must carry the meaning. It does explain that include_readonly controls inclusion of firmware-reserved read-only rules, which is more than the schema gives, but the same 'counted' ambiguity leaves the exact effect of setting it to true unclear.

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 resource precisely — configured port-forwarding rules — and further breaks it into user rules and UPnP rules, which tells an agent what class of objects comes back. It lacks an explicit verb ('list' is only in the name/title), but the scope is unambiguous and distinct from siblings like list_devices or list_dns_records.

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 versus alternatives, and no prerequisites or exclusions are stated. An agent must infer usage entirely from the tool name and the one filter mentioned.

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