Skip to main content
Glama
itunified-io

mcp-opnsense

by itunified-io

opnsense_firmware_upgrade

Initiate a firmware upgrade on OPNsense using status report. Requires explicit confirmation; reboot typically follows.

Instructions

Trigger an OPNsense system upgrade based on what 'opnsense_firmware_status' reports (minor packages, or a major-series jump such as 24.7 → 25.1). Long-running: poll progress with 'opnsense_firmware_upgrade_status'. A reboot is typically required afterwards. DESTRUCTIVE: requires explicit confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmYesMust be true to confirm the upgrade

Implementation Reference

  • UpgradeSchema – Zod schema validating that 'confirm' must be true before proceeding with the system upgrade.
    const UpgradeSchema = z.object({
      confirm: ConfirmTrue("confirm must be true to proceed with the system upgrade"),
    });
  • Tool definition for 'opnsense_firmware_upgrade' including description and input schema (confirm boolean required).
    {
      name: "opnsense_firmware_upgrade",
      description:
        "Trigger an OPNsense system upgrade based on what 'opnsense_firmware_status' reports (minor packages, or a major-series jump such as 24.7 → 25.1). Long-running: poll progress with 'opnsense_firmware_upgrade_status'. A reboot is typically required afterwards. DESTRUCTIVE: requires explicit confirmation.",
      inputSchema: {
        type: "object" as const,
        properties: {
          confirm: {
            type: "boolean",
            description: "Must be true to confirm the upgrade",
            enum: [true],
          },
        },
        required: ["confirm"],
      },
    },
  • Handler case 'opnsense_firmware_upgrade' – validates args against UpgradeSchema, then POSTs to '/core/firmware/upgrade' via OPNsenseClient and returns JSON result.
    case "opnsense_firmware_upgrade": {
      UpgradeSchema.parse(args);
      const result = await client.post("/core/firmware/upgrade");
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • src/index.ts:66-66 (registration)
    Registration: maps the firmware tool definitions (including 'opnsense_firmware_upgrade') to handleFirmwareTool handler via the toolHandlers map.
    for (const def of firmwareToolDefinitions) toolHandlers.set(def.name, handleFirmwareTool);
Behavior4/5

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

With no annotations provided, the description carries the full burden and discloses key behavioral traits: destructive nature, requirement for explicit confirmation (via confirm parameter), long-running operation, and typical need for reboot. It could mention error handling or cancellation, but covers the major risks.

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 extremely concise: two sentences plus a warning. It front-loads the purpose and includes all critical information without unnecessary words. Every sentence adds value.

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

Completeness4/5

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

For a destructive, long-running tool with a simple input schema and no output schema, the description explains the trigger, polling mechanism, and aftermath. It lacks explicit mention of the immediate return value, but the reference to polling implies a task identifier is returned. Overall fairly complete for an AI agent.

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

Parameters3/5

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

Schema coverage is 100% with a single 'confirm' parameter. The description reiterates the need for confirmation but adds no new semantic information beyond the schema. Baseline score of 3 is appropriate as the schema already documents the parameter well.

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 tool triggers an OPNsense system upgrade, specifying it is based on firmware status reports and distinguishing between minor and major upgrades. It references sibling tools like opnsense_firmware_status and opnsense_firmware_upgrade_status, differentiating this from other firmware operations.

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 provides clear context on when to use the tool: after checking firmware status, and it tells the agent to poll progress with a sibling tool and expect a reboot. It does not explicitly state when NOT to use it, but the context is sufficient for an AI agent to infer appropriate usage.

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