Skip to main content
Glama
itunified-io

mcp-opnsense

by itunified-io

opnsense_dns_infra

Diagnose upstream DNS connectivity issues by dumping the Unbound infrastructure cache, including upstream server RTT, EDNS support, and lame delegation status.

Instructions

Dump the Unbound infrastructure cache showing upstream server RTT, EDNS support, and lame delegation status. Useful for diagnosing upstream DNS connectivity issues.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'opnsense_dns_infra' tool. It calls the OPNsense Unbound diagnostics API endpoint '/unbound/diagnostics/dumpinfra' to dump the infrastructure cache showing upstream server RTT, EDNS support, and lame delegation status. Returns the raw JSON result.
    case "opnsense_dns_infra": {
      const result = await client.get("/unbound/diagnostics/dumpinfra");
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • The tool definition/schema for 'opnsense_dns_infra'. It declares the tool name, description ('Dump the Unbound infrastructure cache...'), and an empty inputSchema (no parameters required).
      name: "opnsense_dns_infra",
      description:
        "Dump the Unbound infrastructure cache showing upstream server RTT, EDNS support, and lame delegation status. Useful for diagnosing upstream DNS connectivity issues.",
      inputSchema: { type: "object" as const, properties: {} },
    },
  • src/index.ts:26-26 (registration)
    Import of dnsToolDefinitions from the dns.ts file, which includes the opnsense_dns_infra definition.
    import { dnsToolDefinitions, handleDnsTool } from './tools/dns.js';
  • src/index.ts:59-59 (registration)
    Registration of the DNS tool handler: all dnsToolDefinitions (including opnsense_dns_infra) are mapped 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?

No annotations are provided, but the description makes it clear this is a read-only dump operation with no destructive side effects. It does not mention authentication or rate limits, but for a simple diagnostic tool, this is adequate.

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 two sentences, front-loading the action and then adding context. No unnecessary words. Every sentence earns its place.

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 tool with no output schema, the description covers purpose and use case adequately. It could hint at the return format or raw data nature, but the information given is sufficient for an AI agent to understand when to invoke it.

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 no parameters, and the input schema has 100% coverage. The description does not need to add parameter information. A baseline of 4 is appropriate.

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 dumps the Unbound infrastructure cache, specifying the exact data (RTT, EDNS support, lame delegation status). This is a specific verb+resource, distinguishing it from siblings like opnsense_dns_cache_search which searches cache entries.

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 explicitly says 'Useful for diagnosing upstream DNS connectivity issues,' providing a clear use case. However, it lacks explicit exclusions or alternatives, though the context of siblings implies when to use this tool vs. others.

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