Skip to main content
Glama
itunified-io

mcp-opnsense

by itunified-io

opnsense_acme_apply

Apply pending ACME configuration changes to reconfigure the ACME service on your OPNsense firewall.

Instructions

Apply pending ACME configuration changes (reconfigure service)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool definition (schema) for opnsense_acme_apply — no input parameters, description is 'Apply pending ACME configuration changes (reconfigure service)'
    {
      name: "opnsense_acme_apply",
      description: "Apply pending ACME configuration changes (reconfigure service)",
      inputSchema: { type: "object" as const, properties: {} },
    },
  • Handler case for opnsense_acme_apply — sends POST to /acmeclient/service/reconfigure to apply pending ACME config changes
    case "opnsense_acme_apply": {
      const result = await client.post("/acmeclient/service/reconfigure");
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • src/index.ts:65-65 (registration)
    Registers the handleAcmeTool function as the handler for all ACME tools including opnsense_acme_apply
    for (const def of acmeToolDefinitions) toolHandlers.set(def.name, handleAcmeTool);
  • src/index.ts:46-46 (registration)
    acmeToolDefinitions array is spread into allToolDefinitions for MCP tool registration
    ...acmeToolDefinitions,
Behavior4/5

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

The description mentions 'reconfigure service', which hints at potential side effects like service restart or reload. With no annotations provided, this level of disclosure is adequate for a simple action. However, it could be more explicit about whether it applies all pending changes or just specific ones, and whether it is safe to call multiple times.

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, front-loaded sentence with no filler: 'Apply pending ACME configuration changes (reconfigure service)'. Every word earns its place, achieving maximum conciseness.

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?

Given the tool has no parameters and no output schema, the description is complete for an agent to understand its purpose and effect. The sibling tools provide additional context, but the description alone is sufficient for this simple action.

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?

There are no parameters, and the schema coverage is 100%. The description does not need to add parameter semantics. Baseline for zero parameters 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?

The description clearly states the tool applies pending ACME configuration changes and reconfigures the service. It uses a specific verb ('apply') and resource ('ACME configuration changes'), and effectively distinguishes it from sibling ACME tools that handle accounts, certificates, or challenges, as well as other apply tools for different services.

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 implicitly indicates usage after making ACME configuration changes, but does not explicitly state when to use it versus alternatives or prerequisites. For a zero-parameter apply tool, the context is clear enough, but explicit guidance on when not to use or sequencing with other ACME tools would improve 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