Skip to main content
Glama

put_lan_browser_interface_hostid

Update a LAN host's properties on a specific interface, including device type, name, and network settings.

Instructions

Update a LanHost properties

Error codes: noent, internal_error, ioerror, inval, inval_gateway_ip, nodev, nohost, nomem, netdown

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
interfaceYes
hostidYes
idNoHost id (unique on this interface)
primary_nameNoHost primary name (chosen from the list of available names, or manually set by user)
host_typeNoWhen possible, the Freebox will try to guess the host_type, but you can manually override this to the correct value — Values: `workstation`: Workstation; `laptop`: Laptop; `smartphone`: Smartphone; `tablet`: Tablet; `printer`: Printer; `vg_console`: Video game console; `television`: TV; `nas`: Nas; `ip_camera`: IP Camera; `ip_phone`: IP Phone; `freebox_player`: Freebox Player; `freebox_hd`: Freebox Server; `networking_device`: Networking device; `multimedia_device`: Multimedia device; `other`: Other
primary_name_manualNoIf true the primary name has been set manually
l2identNoLayer 2 network id and its type
vendor_nameNoHost vendor name (from the mac address)
persistentNoIf true the host is always shown even if it has not been active since the Freebox startup
reachableNoIf true the host can receive traffic from the Freebox
last_time_reachableNoLast time the host was reached — Unix timestamp (seconds since epoch).
activeNoIf true the host sends traffic to the Freebox
last_activityNoLast time the host sent traffic — Unix timestamp (seconds since epoch).
namesNoList of available names, and their source
l3connectivitiesNoList of available layer 3 network connections

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'Update' and lists error codes, but does not disclose whether updates are partial or full, if authentication is required, or any side effects. The error codes hint at possible failures but lack context.

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 short (two lines) and front-loaded with purpose. However, the error code list takes space but is not explained. It is concise but at the cost of completeness.

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 15 parameters, no output schema described, and no annotations, the description is too sparse. It fails to explain what the output is, prerequisites, or how parameters relate. The listed error codes are not contextualized.

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 87%, so the schema itself describes most parameters well. The description adds no additional meaning beyond restating that it updates properties. Baseline 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 'Update a LanHost properties', which is a specific verb+resource. It distinguishes from sibling 'get_lan_browser_interface_hostid' which retrieves. However, it does not elaborate on which properties are updatable beyond what the schema provides.

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 given on when to use this tool versus alternatives. There is no mention of prerequisites, context, or when not to use it. The sibling list contains many other put operations, but no differentiation is provided.

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