pfSense MCP Server

update_dhcp_static_mapping

Idempotent

Update an existing DHCP static mapping by ID, changing only the provided fields such as IP, MAC, hostname, or lease times while retaining others. Apply changes immediately or defer.

Instructions

Update an existing DHCP static mapping by ID

Only the parameters you pass are sent, so unset ones keep their stored values.

Input Schema

TableJSON Schema

Name	Required	Description
`hostname`	No	New hostname
`interface`	No	New interface/DHCP pool
`ip_address`	No	New IP address
`mapping_id`	Yes	Static mapping ID
`description`	No	New description
`mac_address`	No	New MAC address
`max_lease_time`	No	New per-host maximum lease time in seconds
`apply_immediately`	No	Whether to apply changes immediately
`default_lease_time`	No	New per-host default lease time in seconds

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.1.0Sep 26, 2026

addedInput schema / properties / default_lease_time

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "New per-host default lease time in seconds"
+}

addedInput schema / properties / max_lease_time

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "New per-host maximum lease time in seconds"
+}

First observedv1.0.0Aug 9, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds an important behavioral detail beyond annotations: 'Only the parameters you pass are sent, so unset ones keep their stored values.' This clarifies partial-update semantics and prevents an agent from assuming omitted fields will be cleared. This is especially valuable because all optional parameters default to null.

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

Conciseness5/5

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

The description is two sentences: the first states the core function, and the second conveys the critical partial-update behavior. It is concise, front-loaded, and contains no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the annotations, full schema coverage, and existing output schema, the description provides the essential extra context needed to invoke the tool correctly. It identifies the object by ID and explains the update semantics. No critical behavioral information is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameter descriptions already exist for every field. The description adds the key semantic that omitted parameters are not reset, which directly affects how an agent should interpret the optional fields. This goes beyond the schema's individual field descriptions.

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

Purpose5/5

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

The description clearly states the action ('Update') and the target resource ('existing DHCP static mapping by ID'). It is easy to distinguish from sibling tools like create_dhcp_static_mapping, delete_dhcp_static_mapping, and search_dhcp_static_mappings.

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

Usage Guidelines4/5

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

The phrase 'existing DHCP static mapping by ID' provides clear context that this tool is for modifying an already-created mapping. It does not explicitly exclude alternatives, but the intent is unambiguous enough for an agent to select it appropriately.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server