Skip to main content
Glama
itunified-io

mcp-opnsense

by itunified-io

opnsense_svc_control

Start, stop, or restart any OPNsense service by name, providing direct control over firewall services via the REST API.

Instructions

Start, stop, or restart a service by name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
service_nameYesName of the service (e.g. 'unbound', 'openssh', 'configd')
actionYesAction to perform on the service

Implementation Reference

  • Handler case for 'opnsense_svc_control' — parses args with ServiceControlSchema, calls POST /core/service/{action}/{service_name}, and returns the result as JSON.
    case "opnsense_svc_control": {
      const parsed = ServiceControlSchema.parse(args);
      const result = await client.post(
        `/core/service/${parsed.action}/${encodeURIComponent(parsed.service_name)}`,
      );
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • ServiceControlSchema — Zod object validating service_name (string) and action (start/stop/restart enum).
    const ServiceControlSchema = z.object({
      service_name: z.string().min(1, "Service name is required"),
      action: ServiceActionSchema,
    });
  • ServiceActionSchema — Zod enum allowing 'start', 'stop', or 'restart' actions.
    export const ServiceActionSchema = z.enum(["start", "stop", "restart"]);
  • Tool definition registration — declares 'opnsense_svc_control' with name, description, and inputSchema (service_name, action).
    {
      name: "opnsense_svc_control",
      description: "Start, stop, or restart a service by name",
      inputSchema: {
        type: "object" as const,
        properties: {
          service_name: {
            type: "string",
            description: "Name of the service (e.g. 'unbound', 'openssh', 'configd')",
          },
          action: {
            type: "string",
            enum: ["start", "stop", "restart"],
            description: "Action to perform on the service",
          },
        },
        required: ["service_name", "action"],
      },
    },
  • src/index.ts:64-64 (registration)
    Registration: maps 'opnsense_svc_control' to handleSystemTool in the toolHandlers map.
    for (const def of systemToolDefinitions) toolHandlers.set(def.name, handleSystemTool);
Behavior2/5

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

No annotations are provided. The description indicates a mutation operation but does not disclose potential side effects, error conditions, or permission requirements. Minimal behavioral context beyond the obvious.

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, efficient sentence with no redundant words. It is concise and directly to the point.

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 tool with two clear parameters and no output schema, the description covers the core functionality. However, it does not mention return values or confirmation of action, which might be expected.

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% and clearly defines both parameters with descriptions and an enum for action. The description adds no meaningful extra meaning beyond what the schema provides.

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 and resource: 'Start, stop, or restart a service by name.' It specifies the actions and the target, distinguishing it from sibling tools like 'opnsense_svc_list'.

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?

The description provides no guidance on when to use this tool versus other service-related tools. No mention of prerequisites, alternatives, or when not to use it.

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