Skip to main content
Glama

put_fw_incoming_port_id

Update properties of an incoming port configuration, such as port number, protocol, or enabled status, for services like HTTP, VPN, or FTP on your Freebox server.

Instructions

Update a IncomingPortConfig properties

Error codes: noent, internal_error, exist

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
port_idYes
idNoincoming port id — Values: `http`: http port for remote access to Freebox OS; `https`: https port for tls remote access to Freebox OS; `bittorrent-main`: main bittorrent port for Freebox downloader; `bittorrent-dht`: bittorrent port for DHT; `openvpn_routed`: routed openvpn port; `openvpn_bridge`: bridged openvpn port; `ipsec_ike`: ipsec ikev2 vpn port; `ipsec_nat`: ipsec nat vpn port; `pptp`: pptp vpn server port; `ftp`: ftp control port for FTP remote access; `ftp_pasv`: ftp data port for FTP remote access
enabledNois the port binding allowed
activeNois the port binding currently active
typeNoValues: `tcp`: TCP; `udp`: UDP; `tcp_udp`: both TCP and UDP
in_portNobinding port
netnsNonetwork namespace. The service may be running on a different namespace (for instance if the service uses the vpn client).
min_portNoThis field indicate the minimum possible value for in_port (see ConnectionStatus ipv4_port_range)
max_portNoThis field indicate the maximum possible value for in_port (see ConnectionStatus ipv4_port_range)
readonlyNoIf set to true, the in_port field cannot be changed because of the underlying protocol does not allow it

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

The description lists three error codes ('noent', 'internal_error', 'exist'), which provides some behavioral insight. However, with no annotations, the description fails to disclose whether the update is a full replacement or partial, side effects, or idempotency. It lacks detail on success behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is extremely brief (one sentence plus error codes). While concise, it sacrifices completeness and structure. It should provide more detail without being verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool complexity (10 parameters, mutative operation), the description is insufficient. It does not explain the overall behavior, output schema, or how parameters interact. Sibling tools exist but no guidance is given.

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?

With 90% schema description coverage, the input schema already explains most parameters thoroughly (e.g., 'id' has enumerated values with explanations). The description adds no semantic value beyond the schema; baseline score of 3 is appropriate.

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 clearly states the verb 'Update' and the resource 'IncomingPortConfig', which conveys the primary action. However, it does not distinguish this tool from other put tools for firewall configuration (e.g., put_fw_redir_redir_id), and the phrase 'properties' is vague.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., when to use get_fw_incoming_port_id first, or how this differs from put_fw_redir_redir_id). There are no prerequisites, conditions, or contextual hints.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nelson-PROIA/freebox-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server