Skip to main content
Glama
itunified-io

mcp-opnsense

by itunified-io

opnsense_sys_list_certs

List all certificates in the OPNsense trust store, including refids, descriptions, and validity dates, to audit certificate status.

Instructions

List all certificates in the OPNsense trust store with their refids, descriptions, and validity dates

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for opnsense_sys_list_certs: calls GET /trust/cert/search on the OPNsense API and returns JSON result.
    case "opnsense_sys_list_certs": {
      const result = await client.get("/trust/cert/search");
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • Tool definition registration: name 'opnsense_sys_list_certs' with description and empty inputSchema, exported in systemToolDefinitions array.
    {
      name: "opnsense_sys_list_certs",
      description:
        "List all certificates in the OPNsense trust store with their refids, descriptions, and validity dates",
      inputSchema: { type: "object" as const, properties: {} },
    },
  • src/index.ts:64-64 (registration)
    Mapping of systemToolDefinitions (including opnsense_sys_list_certs) to handleSystemTool handler in the MCP server setup.
    for (const def of systemToolDefinitions) toolHandlers.set(def.name, handleSystemTool);
Behavior3/5

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

With no annotations, the description carries the entire burden. It states the tool lists certificates, implying a read-only operation, but does not disclose potential prerequisites, authentication needs, or whether the trust store is local or remote. For a simple list tool, this is adequate but not enriched.

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 sentence with no wasted words, front-loaded with the action verb 'List'. It efficiently communicates the tool's purpose and output.

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?

Given the tool has no parameters and no output schema, the description specifies the resource ('OPNsense trust store') and the returned fields (refids, descriptions, validity dates). This is sufficient for an agent to understand what the tool returns. Minor omission: no mention of potential limits or pagination, but these are unlikely for a certificate list.

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?

The tool has zero parameters, and the input schema is fully covered (100% empty). The description does not need to add parameter meaning. The baseline score for no parameters is 4, and the description meets it without needing extra detail.

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 uses a specific verb ('List') and clearly identifies the resource ('certificates in the OPNsense trust store') and the returned fields (refids, descriptions, validity dates). It distinguishes from sibling tools because no other tool lists trust store certificates; ACME tools list ACME-managed certs, not the system trust store.

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?

The description implies it is for viewing all trust store certificates, but it does not explicitly state when to use it versus alternatives (e.g., ACME certificate listing). While no direct competitor exists, providing context about its scope vs. ACME tools would improve guidance.

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