Skip to main content
Glama
itunified-io

mcp-opnsense

by itunified-io

opnsense_dns_list_forwards

Lists all DNS-over-TLS forwarding servers configured in Unbound. Retrieve current forwarder settings for review or auditing.

Instructions

List all DNS-over-TLS forwarding servers configured in Unbound

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler that executes the tool by calling GET /api/unbound/settings/searchDot on the OPNsense API and returning the JSON result.
    case "opnsense_dns_list_forwards": {
      const result = await client.get("/unbound/settings/searchDot");
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • Schema/definition for the tool: no input parameters required, lists all DNS-over-TLS forwarding servers.
    {
      name: "opnsense_dns_list_forwards",
      description: "List all DNS-over-TLS forwarding servers configured in Unbound",
      inputSchema: { type: "object" as const, properties: {} },
  • src/index.ts:40-40 (registration)
    The tool definition is spread into allToolDefinitions used for ListTools.
    ...dnsToolDefinitions,
  • src/index.ts:59-59 (registration)
    Registration: maps 'opnsense_dns_list_forwards' to handleDnsTool in the toolHandlers map.
    for (const def of dnsToolDefinitions) toolHandlers.set(def.name, handleDnsTool);
Behavior4/5

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

Description indicates a read-only list operation. With no annotations, it effectively conveys the non-destructive nature. No additional behavioral details are needed for this simple tool.

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 sentence is concise and front-loaded with the action and resource. No superfluous words.

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?

For a parameterless list tool with no output schema, the description fully captures the tool's purpose and behavior. No additional context is required.

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?

No parameters are present, and schema coverage is 100%. Description adds no parameter-specific information, which is acceptable as there are no parameters to describe.

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?

Description clearly states 'List all DNS-over-TLS forwarding servers configured in Unbound' with a specific verb and resource, distinguishing it from sibling tools like opnsense_dns_add_forward.

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 implies use for retrieving existing forwards, but does not explicitly state when not to use or mention alternatives. Context is clear enough given the simplicity of the tool.

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