io.github.antonio-mello-ai/mcp-pfsense

delete_dhcp_static_mapping

Remove a DHCP static mapping on pfSense by interface and mapping ID, with confirmation required and options to stage or apply changes immediately.

Instructions

Delete a DHCP static mapping. Requires confirm=true.

interface is the mapping's DHCP server — the parent_id value returned by list_dhcp_static_mappings; mapping_id is its id there. Staged until apply_changes('dhcp') is called or apply=true is passed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`apply`	No
`confirm`	No
`interface`	Yes
`mapping_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.3.0Sep 26, 2026

addedInput schema / properties / apply

Added value: +{
+  "default": false,
+  "title": "Apply",
+  "type": "boolean"
+}

addedInput schema / properties / interface

Added value: +{
+  "title": "Interface",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "mapping_id"
-]New value: +[
+  "interface",
+  "mapping_id"
+]

First observedv0.1.1Jun 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, the description carries the full transparency burden. It clearly discloses that the delete requires confirmation, is staged rather than immediately destructive, and can be made permanent via apply_changes or apply=true. This is strong behavioral disclosure for a destructive mutation tool.

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 compact and front-loaded: action, required flag, parameter semantics, then staging behavior. Each sentence earns its place and the backtick formatting makes the key identifiers and values easy to scan. There is no redundant 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?

For a four-parameter mutation tool with no annotations and an output schema present, the description is complete: it states what is deleted, the required confirmation, how to identify the correct interface and mapping, and how to commit or stage the change. An agent has everything needed to call it correctly.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate. It does: interface is explained as the mapping's DHCP server and the parent_id from list_dhcp_static_mappings, while mapping_id is its id in that listing. It also explains the roles of confirm and apply. This is far more than the schema alone provides.

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 opens with a specific action and resource: 'Delete a DHCP static mapping.' This directly distinguishes it from sibling delete tools like delete_firewall_rule and delete_dns_host_override. It also adds essential behavior context (confirm and staging) rather than merely restating the tool name.

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 description gives clear operational guidance: confirm=true is required, and the delete is staged until apply_changes('dhcp') or apply=true. It also points to list_dhcp_static_mappings for finding identifiers. It does not explicitly state when not to use this tool, but the prerequisites and workflow are clear enough for an agent to select and invoke it correctly.

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