Update a static DHCP lease by its ID to modify lease parameters on a 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 |
|---|---|---|---|
| id | Yes | ||
| body | No |
Changes observed during successful MCP inspections.
v0.1.1Input schema / properties / id / typePrevious value: -"integer"New value: +"string"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 / id / descriptionRemoved value: -"DHCP static lease object id"Input schema / properties / id / typePrevious value: -"string"New value: +"integer"Input schema / properties / id__pathRemoved value: -{
- "description": "DHCP static lease object id (the host mac address) (Path parameter)",
- "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"
-}Input schema / requiredPrevious value: -[
- "id__path"
-]New value: +[
+ "id"
+]Output schema / (root)Previous value: -{
- "additionalProperties": true,
- "type": "object"
-}New value: +nullv0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description should disclose behavioral traits. It only lists possible error codes, which is partially transparent but omits side effects, auth requirements, or whether the operation is destructive. The error codes hint at potential 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short (one line of error codes), but this is underspecification, not conciseness. It fails to provide any meaningful information about the tool's purpose or usage.
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 lack of output schema, nested body parameter, and many sibling tools, the description is severely incomplete. It does not explain the tool's role, input semantics, or appropriate contexts, making it nearly useless for an AI agent.
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 two parameters (id and body) with 0% schema description coverage. The description adds no explanation of what 'id' represents (likely the lease ID) or what 'body' contains (lease properties). This is a critical gap.
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 state the tool's purpose. It fails to indicate that this tool updates a DHCP static lease, which is essential for an agent to understand its function.
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 is provided on when to use this tool versus siblings like 'post_dhcp_static_lease' or 'delete_dhcp_static_lease_id'. The context for usage is entirely absent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.