Create a static DHCP lease to assign a fixed IP address to a device on your Freebox network.
Error codes: inval, inval_netmask, inval_ip_range, inval_ip_range_net, inval_gw_net, exist, nodev, noent, netdown, busy
| Name | Required | Description | Default |
|---|---|---|---|
| body | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / properties / bodyAdded value: +{
+ "additionalProperties": true,
+ "type": "object"
+}Input schema / properties / commentRemoved value: -{
- "description": "an optional comment",
- "type": "string"
-}Input schema / properties / hostRemoved value: -{
- "description": "LAN host information from LAN browser (refer to LanHost documentation)",
- "properties": {
- "active": {
- "description": "If true the host sends traffic to the Freebox",
- "type": "boolean"
- },
- "host_type": {
- "description": "When 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",
- "enum": [
- "workstation",
- "laptop",
- "smartphone",
- "tablet",
- "printer",
- "vg_console",
- "television",
- "nas",
- "ip_camera",
- "ip_phone",
- "freebox_player",
- "freebox_hd",
- "networking_device",
- "multimedia_device",
- "other"
- ],
- "type": "string"
- },
- "id": {
- "description": "Host id (unique on this interface)",
- "type": "string"
- },
- "l2ident": {
- "description": "Layer 2 network id and its type",
- "items": {
- "description": "Lan Host has the following attributes:",
- "properties": {
- "id": {
- "description": "Layer 2 id",
- "type": "string"
- },
- "type": {
- "description": "Values: `dhcp`: DHCP; `netbios`: Netbios; `mdns`: mDNS; `upnp`: UPnP",
- "enum": [
- "dhcp",
- "netbios",
- "mdns",
- "upnp"
- ],
- "type": "string"
- }
- },
- "type": "object"
- },
- "type": "array"
- },
- "l3connectivities": {
- "description": "List of available layer 3 network connections",
- "items": {
- "description": "Lan Host has the following attributes:",
- "properties": {
- "active": {
- "description": "is the connection active",
- "type": "boolean"
- },
- "addr": {
- "description": "Layer 3 address",
- "type": "string"
- },
- "af": {
- "description": "Values: `ipv4`: IPv4; `ipv6`: IPv6",
- "enum": [
- "ipv4",
- "ipv6"
- ],
- "type": "string"
- },
- "last_activity": {
- "description": "last activity timestamp — Unix timestamp (seconds since epoch).",
- "type": "integer"
- },
- "last_time_reachable": {
- "description": "last reachable timestamp — Unix timestamp (seconds since epoch).",
- "type": "integer"
- },
- "reachable": {
- "description": "is the connection reachable",
- "type": "boolean"
- }
- },
- "type": "object"
- },
- "type": "array"
- },
- "last_activity": {
- "description": "Last time the host sent traffic — Unix timestamp (seconds since epoch).",
- "type": "integer"
- },
- "last_time_reachable": {
- "description": "Last time the host was reached — Unix timestamp (seconds since epoch).",
- "type": "integer"
- },
- "names": {
- "description": "List of available names, and their source",
- "items": {
- "description": "Lan Host has the following attributes:",
- "properties": {
- "name": {
- "description": "Host name",
- "type": "string"
- },
- "source": {
- "description": "source of the name",
- "type": "string"
- }
- },
- "type": "object"
- },
- "type": "array"
- },
- "persistent": {
- "description": "If true the host is always shown even if it has not been active since the Freebox startup",
- "type": "boolean"
- },
- "primary_name": {
- "description": "Host primary name (chosen from the list of available names, or manually set by user)",
- "type": "string"
- },
- "primary_name_manual": {
- "description": "If true the primary name has been set manually",
- "type": "boolean"
- },
- "reachable": {
- "description": "If true the host can receive traffic from the Freebox",
- "type": "boolean"
- },
- "vendor_name": {
- "description": "Host vendor name (from the mac address)",
- "type": "string"
- }
- },
- "type": "object"
-}Input schema / properties / hostnameRemoved value: -{
- "description": "hostname matching the mac address",
- "type": "string"
-}Input schema / properties / idRemoved value: -{
- "description": "DHCP static lease object id",
- "type": "string"
-}Input schema / properties / ipRemoved value: -{
- "description": "IPv4 to assign to the host",
- "type": "string"
-}Input schema / properties / macRemoved value: -{
- "description": "Host mac address",
- "type": "string"
-}v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description fails to disclose any behavioral traits (e.g., that it creates a resource, requires authorization, or has side effects). Only error codes are listed, which 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
While the description is short, it is not appropriately sized because it omits essential information. Every sentence is wasted on a list of error codes without context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of DHCP static lease creation and the presence of many error codes, the description is completely inadequate. It fails to explain the tool's purpose, usage, or parameter semantics.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has one optional 'body' parameter with additionalProperties, and schema description coverage is 0%. The description does not explain what the body should contain, leaving the agent without guidance on parameter structure.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description only lists error codes and does not specify what the tool does. The tool name suggests creating a DHCP static lease, but the description provides no verb or resource.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 like put_dhcp_static_lease_id. The description is entirely missing usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.