Skip to main content
Glama
itunified-io

mcp-opnsense

by itunified-io

opnsense_firmware_install

Install an OPNsense plugin package by specifying its name, such as 'os-acme-client' or 'os-haproxy'. May require a service restart.

Instructions

Install an OPNsense plugin package by name (e.g. 'os-acme-client'). May require a service restart.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageYesPlugin package name (e.g. 'os-acme-client', 'os-haproxy')

Implementation Reference

  • Handler case for opnsense_firmware_install: validates args with PackageSchema, then POSTs to /core/firmware/install/{package} via OPNsenseClient.
    case "opnsense_firmware_install": {
      const parsed = PackageSchema.parse(args);
      const result = await client.post("/core/firmware/install/" + encodeURIComponent(parsed.package));
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • Zod schema validating that the 'package' argument is a non-empty string.
    const PackageSchema = z.object({
      package: z.string().min(1, "Package name is required"),
    });
  • Tool definition registration in firmwareToolDefinitions array, listing name, description, and inputSchema.
    {
      name: "opnsense_firmware_install",
      description:
        "Install an OPNsense plugin package by name (e.g. 'os-acme-client'). May require a service restart.",
      inputSchema: {
        type: "object" as const,
        properties: {
          package: {
            type: "string",
            description: "Plugin package name (e.g. 'os-acme-client', 'os-haproxy')",
          },
        },
        required: ["package"],
      },
    },
  • src/index.ts:66-66 (registration)
    Maps the firmware tool name to the handleFirmwareTool handler function in the central toolHandlers map.
    for (const def of firmwareToolDefinitions) toolHandlers.set(def.name, handleFirmwareTool);
  • OPNsenseClient.post helper used to make the HTTP POST request to the OPNsense firmware install API endpoint.
    async post<T>(path: string, data?: unknown): Promise<T> {
      try {
        const response = await this.http.post<T>(path, data ?? {}, {
          headers: { "Content-Type": "application/json" },
        });
        return response.data;
      } catch (error: unknown) {
        throw extractError(error, `POST ${path}`);
      }
    }
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that a service restart may be required, which is helpful. However, it does not detail other potential behaviors (e.g., whether the service restarts automatically, permissions needed, or rollback).

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?

Two short sentences, front-loaded with the key action and object. Every word is necessary, no fluff. Perfectly concise.

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?

Given the low complexity (1 parameter, no output schema), the description is mostly complete. It states the purpose, provides an example, and notes a restart caveat. Missing details about return values or post-install state, but acceptable for the tool's simplicity.

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?

The input schema already provides 100% coverage for the single parameter 'package', including an example. The description adds no new meaning beyond restating 'by name'. Baseline 3 is appropriate since schema does the heavy lifting.

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 ('Install') and the resource ('OPNsense plugin package by name'), with an example ('os-acme-client'). It immediately distinguishes itself from sibling tools like opnsense_firmware_remove or opnsense_firmware_upgrade.

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

Usage Guidelines3/5

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

The description implies usage (use when you want to install a plugin), but does not explicitly state when to avoid it or when to use an alternative sibling like opnsense_firmware_upgrade instead. No exclusions or context are provided.

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