Skip to main content
Glama
itunified-io

mcp-opnsense

by itunified-io

opnsense_acme_add_account

Register a new ACME account with a certificate authority to automate certificate renewal and configuration.

Instructions

Register a new ACME account with a certificate authority (Let's Encrypt, ZeroSSL, etc.). Run opnsense_acme_apply afterwards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesAccount name (e.g. 'Let\'s Encrypt Production')
emailYesContact email address for the account
caNoCertificate authority (default: letsencrypt)

Implementation Reference

  • Handler for opnsense_acme_add_account: parses input via AddAccountSchema, sends POST to /acmeclient/accounts/add with account fields (enabled, name, email, ca), returns JSON result.
    case "opnsense_acme_add_account": {
      const parsed = AddAccountSchema.parse(args);
      const result = await client.post("/acmeclient/accounts/add", {
        account: {
          enabled: "1",
          name: parsed.name,
          email: parsed.email,
          ca: parsed.ca,
        },
      });
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • Zod schema for input validation: requires name (non-empty) and email (valid email), optional ca defaults to letsencrypt.
    const AddAccountSchema = z.object({
      name: z.string().min(1, "Account name is required"),
      email: z.string().email("Valid email address is required"),
      ca: z.enum([
        "letsencrypt",
        "letsencrypt-staging",
        "zerossl",
        "buypass",
        "buypass-test",
        "sslcom",
        "google",
        "googletest",
      ], { message: "Unsupported certificate authority" }).optional().default("letsencrypt"),
    });
  • Tool registration in acmeToolDefinitions array with name, description, and inputSchema (name, email required; ca optional enum).
    {
      name: "opnsense_acme_add_account",
      description:
        "Register a new ACME account with a certificate authority (Let's Encrypt, ZeroSSL, etc.). Run opnsense_acme_apply afterwards.",
      inputSchema: {
        type: "object" as const,
        properties: {
          name: { type: "string", description: "Account name (e.g. 'Let\\'s Encrypt Production')" },
          email: { type: "string", description: "Contact email address for the account" },
          ca: {
            type: "string",
            enum: ["letsencrypt", "letsencrypt-staging", "zerossl", "buypass", "buypass-test", "sslcom", "google", "googletest"],
            description: "Certificate authority (default: letsencrypt)",
          },
        },
        required: ["name", "email"],
      },
    },
  • src/index.ts:65-65 (registration)
    Maps the 'opnsense_acme_add_account' tool name to the handleAcmeTool handler function in the toolHandlers registry.
    for (const def of acmeToolDefinitions) toolHandlers.set(def.name, handleAcmeTool);
Behavior2/5

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

With no annotations, the description carries the full burden for behavioral disclosure. It mentions 'register' (implying creation) but does not reveal whether changes require application, permissions needed, or any side effects. The note about running apply afterwards hints at delayed application but is not explicit.

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 extremely concise: two sentences that state the purpose and a crucial next step. Every word earns its place with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, moderate parameter count (3), and sibling complexity, the description is minimally adequate. It covers the core action but lacks context on account validation, email usage, or response format.

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%, so baseline is 3. The description does not add any parameter-specific meaning beyond what is already in the schema; it only rephrases the CA parameter as 'certificate authority' with examples, which adds minimal value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool registers a new ACME account with a certificate authority and provides examples of CAs (Let's Encrypt, ZeroSSL). However, a sibling tool named 'opnsense_acme_register_account' exists, and the description does not differentiate between them, causing slight confusion.

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 a helpful follow-up action ('Run opnsense_acme_apply afterwards'), but it does not explain when to use this tool versus alternatives like 'opnsense_acme_register_account' 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