Skip to main content
Glama
Sign In
UnifiyMe

UnifiyMe

by lobsterclause
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_port_forward_rules

Retrieve all port forwarding rules configured on your UniFi Network Controller to review, verify, or troubleshoot network traffic access.

Instructions

Get all configured port forwarding 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": "get_port_forward_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations are absent, so the description is the only behavior signal. The verb 'get' clearly implies a read-only, side-effect-free operation, and 'all configured' indicates a full list without filters. However, it does not disclose response format, pagination, permission requirements, or whether disabled rules are included.

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, focused sentence with no filler. It front-loads the verb and resource, and includes the 'all' scope efficiently. Every word carries meaning.

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-only list operation with no output schema, the description covers the essential purpose and scope. It could optionally mention response structure or error behavior, but the low complexity makes this adequate.

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 schema is empty with zero parameters, so there is nothing for the description to add beyond the schema. The phrase 'all configured rules' usefully reinforces that no filters or parameters are required.

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

Purpose5/5

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

States a specific verb ('get'), resource ('port forwarding rules'), and scope ('all configured'). This clearly distinguishes it from sibling mutation tools like ensure/update/delete_port_forward_rule and from related read tools like get_firewall_rules and get_traffic_rules.

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?

Provides no when-to-use guidance or explicit alternatives. An agent cannot tell from the description alone when to choose this over get_firewall_rules or get_traffic_rules, nor are any exclusion conditions mentioned.

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