Skip to main content
Glama
itunified-io

mcp-opnsense

by itunified-io

opnsense_firmware_status

Check OPNsense firmware upgrade status (running, pending, done) from cache. Refresh cache by running a firmware check first if needed.

Instructions

Check for available firmware upgrades and their status (running, pending, done). Reads the cached state — call 'opnsense_firmware_check' first if the cache may be stale.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the 'opnsense_firmware_status' tool logic. It calls client.get('/core/firmware/status') and returns the cached upgrade status as a JSON string.
    case "opnsense_firmware_status": {
      const result = await client.get("/core/firmware/status");
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • The input schema definition for 'opnsense_firmware_status' — it takes no parameters (empty object schema).
    {
      name: "opnsense_firmware_status",
      description:
        "Check for available firmware upgrades and their status (running, pending, done). Reads the cached state — call 'opnsense_firmware_check' first if the cache may be stale.",
      inputSchema: { type: "object" as const, properties: {} },
    },
  • src/index.ts:39-42 (registration)
    All tool definitions including firmwareToolDefinitions are aggregated into allToolDefinitions and exposed via ListToolsRequestSchema handler.
    const allToolDefinitions = [
      ...dnsToolDefinitions,
      ...firewallToolDefinitions,
      ...diagnosticsToolDefinitions,
  • src/index.ts:66-66 (registration)
    The tool handler is registered in the toolHandlers map: handleFirmwareTool is bound to each firmware tool definition name.
    for (const def of firmwareToolDefinitions) toolHandlers.set(def.name, handleFirmwareTool);
  • The OPNsenseClient.get method used by the handler to make the HTTP GET request to the OPNsense API.
    async get<T>(path: string): Promise<T> {
      try {
        const response = await this.http.get<T>(path);
        return response.data;
      } catch (error: unknown) {
        throw extractError(error, `GET ${path}`);
      }
    }
Behavior4/5

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

Discloses it reads cached state and implies no destructive effects, compensating for missing annotations. Could add more detail on cache freshness or auth requirements.

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?

Single sentence with verb first, no wasted words. Efficient and front-loaded.

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 simple read-only tool with no parameters, description covers purpose, cache behavior, relationship to sibling, and output scope, making it 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?

No parameters exist; description correctly adds no parameter info. According to guidelines, 0 params baseline is 4.

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?

Clearly states verb 'check' and resource 'firmware upgrades and their status'. Differentiates from siblings like opnsense_firmware_check by noting it reads cached state, making purpose specific.

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

Usage Guidelines5/5

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

Explicitly advises to call opnsense_firmware_check first if cache may be stale, providing clear when-to-use and when-not-to-use guidance.

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