Skip to main content
Glama
itunified-io

mcp-opnsense

by itunified-io

opnsense_acme_list_accounts

Lists all ACME accounts (e.g., Let's Encrypt, ZeroSSL) configured in the OPNsense ACME client plugin.

Instructions

List all ACME accounts (Let's Encrypt, ZeroSSL, etc.) configured in the os-acme-client plugin

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler case for opnsense_acme_list_accounts. Calls client.get('/acmeclient/accounts/search') and returns the JSON result.
    case "opnsense_acme_list_accounts": {
      const result = await client.get("/acmeclient/accounts/search");
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • DeleteAccountSchema - empty object schema (no input params needed for list accounts, though this is the delete schema). The list_accounts tool has no input schema (empty object).
    const DeleteAccountSchema = z.object({
      uuid: UuidSchema,
    });
  • Tool definition entry in acmeToolDefinitions array, registering 'opnsense_acme_list_accounts' with an empty inputSchema.
    export const acmeToolDefinitions = [
      {
        name: "opnsense_acme_list_accounts",
        description: "List all ACME accounts (Let's Encrypt, ZeroSSL, etc.) configured in the os-acme-client plugin",
        inputSchema: { type: "object" as const, properties: {} },
      },
  • src/index.ts:65-65 (registration)
    Registration of the acme tool definitions into the toolHandlers map, mapping each acme tool name to handleAcmeTool.
    for (const def of acmeToolDefinitions) toolHandlers.set(def.name, handleAcmeTool);
Behavior4/5

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

The description implies a read-only operation ('list all') and specifies the resource type (ACME accounts). No annotations, but the simple verb adequately conveys safety.

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, direct sentence with no superfluous words. Highly efficient.

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 zero parameters and no output schema, the description fully covers what the tool does. No missing information.

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?

No parameters exist, so schema coverage is 100%. The description adds no additional parameter info, but none is needed.

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 it lists all ACME accounts and specifies the plugin (os-acme-client), which distinguishes it from sibling tools like add, delete, or register.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool vs. alternatives, but the purpose is obvious given sibling names (e.g., add/delete/register).

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