Skip to main content
Glama
itunified-io

mcp-opnsense

by itunified-io

opnsense_fw_apply

Apply pending firewall configuration changes on OPNsense to activate queued rules and settings without reboot.

Instructions

Apply pending firewall configuration changes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler case for 'opnsense_fw_apply' — executes the apply by POSTing to /firewall/filter/apply endpoint on the OPNsense API and returns the result.
    case "opnsense_fw_apply": {
      const result = await client.post("/firewall/filter/apply");
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • Tool definition/schema for 'opnsense_fw_apply' — declares name, description, and an empty inputSchema (no parameters required).
    {
      name: "opnsense_fw_apply",
      description: "Apply pending firewall configuration changes",
      inputSchema: { type: "object" as const, properties: {} },
  • src/index.ts:27-27 (registration)
    Imports firewallToolDefinitions and handleFirewallTool from src/tools/firewall.js.
    import { firewallToolDefinitions, handleFirewallTool } from './tools/firewall.js';
  • src/index.ts:60-60 (registration)
    Registers handleFirewallTool as the handler for all firewall tools listed in firewallToolDefinitions, including 'opnsense_fw_apply'.
    for (const def of firewallToolDefinitions) toolHandlers.set(def.name, handleFirewallTool);
Behavior2/5

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

No annotations are present, and the description fails to disclose behavioral traits such as whether the apply causes service disruption, returns success/failure, or requires authentication. The agent is left guessing about side effects.

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 a single, front-loaded sentence that efficiently conveys the tool's purpose without unnecessary words.

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

Completeness3/5

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

As a parameterless apply action with no output schema, the description provides the bare minimum. It lacks information on success indicators, error handling, or confirmation steps, making it only marginally complete.

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?

The input schema has zero parameters, so the description adds no parameter semantics beyond what the schema already conveys. With no parameters, the baseline is high, and the description is sufficient.

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 verb 'apply' and resource 'pending firewall configuration changes', distinguishing it from other apply tools like opnsense_dns_apply or opnsense_route_apply.

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 usage guidance is provided. The description does not indicate when to use this tool versus alternatives, nor does it mention prerequisites or that it should be called after making firewall rule changes.

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/itunified-io/mcp-opnsense'

If you have feedback or need assistance with the MCP directory API, please join our Discord server