Skip to main content
Glama
itunified-io

mcp-opnsense

by itunified-io

opnsense_dns_list_overrides

Retrieve all DNS host overrides including A, AAAA, and CNAME records configured in Unbound.

Instructions

List all DNS host overrides (A/AAAA/CNAME records) configured in Unbound

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools/dns.ts:79-83 (registration)
    Tool definition/registration with name, description, and empty input schema
    {
      name: "opnsense_dns_list_overrides",
      description: "List all DNS host overrides (A/AAAA/CNAME records) configured in Unbound",
      inputSchema: { type: "object" as const, properties: {} },
    },
  • Handler that calls the OPNsense API endpoint /unbound/settings/searchHostOverride to list all DNS host overrides
    case "opnsense_dns_list_overrides": {
      const result = await client.get("/unbound/settings/searchHostOverride");
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • src/index.ts:59-59 (registration)
    Maps opnsense_dns_list_overrides to the handleDnsTool handler in the MCP server tool registry
    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?

No annotations provided; description clearly indicates a read-only listing operation. Does not describe potential limits or pagination, but the simple nature makes it transparent enough.

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, 11 words, no filler. Front-loaded with action and resource.

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?

For a parameterless list tool, description is sufficient. Lacks explicit output schema, but the nature of listing overrides is clear given the context.

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 exist, so schema coverage is 100%. Description adds context about record types (A/AAAA/CNAME) beyond schema. No output schema, but inferred return is a list of overrides.

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?

Clearly specifies the verb 'list', resource 'DNS host overrides', and record types (A/AAAA/CNAME). Distinguishes from sibling tools like opnsense_dns_list_forwards.

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 vs. alternatives. Context implies listing, but does not mention when not to use or compare with other list tools.

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