Skip to main content
Glama

post_freeplug_id_reset

Reset a specific Freeplug powerline adapter on your Freebox network to resolve connectivity issues or reinitialize the device.

Instructions

reset the given Freeplug

Error codes: inval, nomem, nosta, nopeer

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
id__pathYes(Path parameter)
idNoFreeplug unique id
localNoif true the Freeplug is connected directly to the Freebox
net_roleNoValues: `sta`: Freeplug Station; `pco`: Freeplug proxy coordinator; `cco`: Central coordinator
modelNoFreebox Server netbios name
eth_port_statusNoValues: `up`: The ethernet port is up; `down`: The ethernet port is down; `unknown`: The ethernet port state is unknown
eth_full_duplexNoethernet link is full duplex
has_networkNois connected to the network
eth_speedNoethernet port speed
inactiveNoseconds since last activity
net_idNonetwork id
rx_rateNorx rate (from the freeplugs to the “cco” freeplug) (in Mb/s) -1 if not available
tx_rateNotx rate (from the “cco” freeplug to the freeplugs) (in Mb/s) -1 if not available

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations provided, so the description carries the full burden. It discloses error codes but does not explain what happens during reset (e.g., network disruption, data loss, auth requirements). For a potentially destructive operation, this is insufficient.

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 (two lines) but lacks structure. It could be more concise if it were more informative; currently it is under-specified rather than concise. Every sentence should earn its place; the error code list is helpful but not contextualized.

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 13 parameters and an output schema (not shown), the description is too sparse. It fails to explain what parameters are used, what the output indicates, or how to interpret error codes. The tool does not account for the complexity of the input schema.

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 100%, so the schema already documents all parameters. The description adds no extra meaning; it does not indicate which parameters are relevant for the reset action (e.g., local, net_role seem irrelevant). Baseline 3 is appropriate.

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

Purpose3/5

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

The description states 'reset the given Freeplug', which is a verb+resource indicating the tool resets a Freeplug device. However, it is vague—'reset' could mean factory reset, reboot, or something else. Error codes are listed but do not clarify the purpose. No differentiation from siblings.

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

Usage Guidelines1/5

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

No guidance on when to use this tool versus alternatives (e.g., other Freeplug tools like get_freeplug_id or put_wifi_ap_id). No context on prerequisites or when a reset is appropriate.

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