Skip to main content
Glama

put_connection_config

Update the Freebox connection configuration: adjust remote access, ping response, ad blocking, Wake-on-LAN, and other network settings.

Instructions

Updates the ConnectionConfiguration

Error codes: inval, nodev, noent, netdown, busy, invalid_port, insecure_password, invalid_provider, invalid_next_hop

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pingNoshould the Freebox respond to external ping requests
is_secure_passNois the admin password secure enough to enable remote access
remote_accessNoenable/disable HTTP remote access
remote_access_portNoport number to use for remote HTTP access
remote_access_min_portNoThis field indicate the minimum possible value for remote_access_port (see ConnectionStatus ipv4_port_range)
remote_access_max_portNoThis field indicate the maximum possible value for remote_access_port (see ConnectionStatus ipv4_port_range)
remote_access_ipNoIPv4 to use for remote access (can be missing if connection is down)
api_remote_accessNois remote access enabled for apps, or share link
wolNoenable/disable Wake-on-lan proxy
adblockNois ads blocking feature enabled
adblock_not_setNoif set to true adblock setting has never been set by the user
allow_token_requestNoif false, user has disabled new token request. New apps can’t request a new token. Apps that already have a token are still allowed

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 error codes but does not disclose behavioral traits such as idempotency, side effects, or required permissions. With no annotations provided, the description fails to communicate important behavioral context beyond the update action.

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

Conciseness3/5

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

The description is very short, which is concise, but it includes a list of error codes that, while potentially useful, may not be the most critical information. The structure could be improved by front-loading usage context.

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 has 12 parameters and no required fields, the description lacks context on how to use the parameters effectively, what the output schema returns, or typical use cases. The presence of an output schema does not compensate for this lack of guidance.

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 input schema has 100% coverage with descriptions for all 12 parameters. The tool description adds no additional meaning beyond what the schema already provides, so a 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 tool updates the ConnectionConfiguration, specifying the action and resource. However, it does not differentiate this from sibling put tools like put_connection_ddns_provider, which also modify connection settings.

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. The description only includes error codes but does not mention prerequisites, when to apply, or exclude scenarios.

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