Skip to main content
Glama
itunified-io

mcp-opnsense

by itunified-io

opnsense_if_list

Retrieve all network interface names and their device mappings from OPNsense firewall. Useful for identifying interface configurations or troubleshooting network setup.

Instructions

List all network interface names and their device mappings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'opnsense_if_list' tool. Calls OPNsense API endpoint /diagnostics/interface/getInterfaceNames and returns the result as JSON.
    case "opnsense_if_list": {
      const result = await client.get("/diagnostics/interface/getInterfaceNames");
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • Tool definition registration for 'opnsense_if_list' with name, description, and empty inputSchema (no args required).
    {
      name: "opnsense_if_list",
      description: "List all network interface names and their device mappings",
  • src/index.ts:62-62 (registration)
    Registration of handleInterfacesTool as the handler for all interface tool definitions (including opnsense_if_list) in the tool handler map.
    for (const def of interfacesToolDefinitions) toolHandlers.set(def.name, handleInterfacesTool);
  • Input schema for opnsense_if_list: an empty object schema (no parameters required).
    inputSchema: { type: "object" as const, properties: {} },
  • The OPNsenseClient.get() method used by the handler to make the API GET request to /diagnostics/interface/getInterfaceNames.
    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}`);
      }
    }
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the listing function but lacks details on read-only nature, auth requirements, or result format. Adequate but not rich.

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, direct and front-loaded, with no extraneous text. 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?

For a simple list tool with no output schema, description gives the gist (interface names and device mappings). Could hint at output structure but sufficient for common use.

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 and schema coverage is 100%, so description adds no param info. Baseline 4 is appropriate given zero parameters.

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?

Description clearly states verb 'List' and resource 'all network interface names' with specific detail 'device mappings', distinguishing from siblings like opnsense_if_get (single interface) and opnsense_if_stats.

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?

Implies use for listing all interfaces, but does not explicitly contrast with sibling tools opnsense_if_get, opnsense_if_stats, or opnsense_if_configure. Context is clear enough for basic selection.

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