Skip to main content
Glama
itunified-io

mcp-opnsense

by itunified-io

opnsense_dns_diagnostics

Dump the current Unbound DNS cache to diagnose DNS resolution issues.

Instructions

Dump the current Unbound DNS cache for diagnostic purposes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool definition/registration for 'opnsense_dns_diagnostics' in the dnsToolDefinitions array, describing it as 'Dump the current Unbound DNS cache for diagnostic purposes' with no input parameters.
    {
      name: "opnsense_dns_flush_cache",
      description: "Flush the Unbound DNS resolver cache",
      inputSchema: { type: "object" as const, properties: {} },
    },
    {
      name: "opnsense_dns_diagnostics",
      description: "Dump the current Unbound DNS cache for diagnostic purposes",
      inputSchema: { type: "object" as const, properties: {} },
    },
  • Handler implementation: executes GET /unbound/diagnostics/dumpcache and returns the raw result as JSON.
    case "opnsense_dns_diagnostics": {
      const result = await client.get("/unbound/diagnostics/dumpcache");
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • src/index.ts:26-26 (registration)
    Import of dnsToolDefinitions and handleDnsTool from the dns tools module.
    import { dnsToolDefinitions, handleDnsTool } from './tools/dns.js';
  • src/index.ts:59-59 (registration)
    Registration of handleDnsTool as the handler for all DNS tool definitions, including opnsense_dns_diagnostics.
    for (const def of dnsToolDefinitions) toolHandlers.set(def.name, handleDnsTool);
Behavior2/5

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

No annotations provided. The description does not clarify whether dumping is read-only or has side effects, nor does it mention output format or required permissions. For a diagnostic read operation, these details are important.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, front-loaded with key action. Appropriately brief, though could benefit from a second sentence for behavioral clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given lack of annotations, output schema, and sibling differentiation, the description is too minimal. It omits output format, safety, and when to use, leaving the agent underinformed.

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 in input schema, so description adds no param info. Schema coverage is 100%, baseline is 4 per rules.

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 the verb 'dump' and resource 'current Unbound DNS cache' for diagnostic purposes. It distinguishes from sibling tools like opnsense_dns_cache_search (search) and opnsense_dns_flush_cache (flush).

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like opnsense_dns_cache_search or opnsense_dns_stats. Missing context for when a full dump is preferred over search or stats.

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