Skip to main content
Glama

upnp

Destructive

Manage router port mappings by checking status, listing current mappings, and enabling or disabling the mapping service with dry-run and confirmation safeguards.

Instructions

UPnP: action=status|list (switch + current port mappings devices opened) | enable | disable. The router offers no per-mapping delete.

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

Input Schema

NameRequiredDescriptionDefault
applyNofalse (default) = dry run: show the plan, diff, warnings and risk, send nothing. true = send it.
actionNostatus
revealNoShow secrets (passwords/keys) unmasked.
routerNoWhich router (see router_status 'routers'); default main.main
confirm_tokenNoRequired with apply=true for CRITICAL changes: the token from the dry run (valid 5 minutes, bound to the exact plan and current router state).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is partially covered. The description adds real value with the constraint 'The router offers no per-mapping delete,' telling the agent it cannot remove individual device mappings — but it never says which of enable/disable is the destructive action or what disabling does to existing mappings.

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?

Telegraphic, front-loaded and free of filler — every fragment carries information. The phrasing '(switch + current port mappings devices opened)' is awkward enough to cost a point but the sizing is appropriate for the 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?

For a destructive, five-parameter mutation tool with no output schema, the description covers the action semantics and one hard router limitation. It leaves the operational contract — which actions need apply/confirm_token and what the returned mappings look like — to the schema, which is reasonable but not fully compensating.

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?

Schema description coverage is 80%, so the schema already explains apply, reveal, router and confirm_token in detail, and the enum defines the actions. The description only adds meaning for the action parameter (what status/list reports); it adds nothing about the dry-run/confirm-token mechanics that matter most for this destructive tool.

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?

Names the resource (UPnP) and the exact action set (status|list|enable|disable), and clarifies that status/list reports the UPnP switch plus port mappings opened by devices. That distinguishes it from the neighboring port_forwarding tool implicitly, though the sibling is never named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The action list implies when to use each mode (inspect vs toggle), but there is no explicit statement of when to pick this over port_forwarding, or which actions are risky and require the dry-run/confirm flow. Usage is inferred rather than stated.

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