Skip to main content
Glama
itunified-io

mcp-opnsense

by itunified-io

opnsense_dns_flush_cache

Clears the Unbound DNS resolver cache to resolve domain name resolution issues.

Instructions

Flush the Unbound DNS resolver cache

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler case that executes the DNS flush cache logic. It calls client.post('/unbound/service/flushcache') to flush the Unbound DNS resolver cache.
    case "opnsense_dns_flush_cache": {
      const result = await client.post("/unbound/service/flushcache");
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • The tool registration/definition that declares the 'opnsense_dns_flush_cache' tool with its name, description, and empty input schema.
    {
      name: "opnsense_dns_flush_cache",
      description: "Flush the Unbound DNS resolver cache",
      inputSchema: { type: "object" as const, properties: {} },
    },
  • src/index.ts:59-70 (registration)
    The tool handler is registered in the toolHandlers map for all DNS tools, including opnsense_dns_flush_cache.
    for (const def of dnsToolDefinitions) toolHandlers.set(def.name, handleDnsTool);
    for (const def of firewallToolDefinitions) toolHandlers.set(def.name, handleFirewallTool);
    for (const def of diagnosticsToolDefinitions) toolHandlers.set(def.name, handleDiagnosticsTool);
    for (const def of interfacesToolDefinitions) toolHandlers.set(def.name, handleInterfacesTool);
    for (const def of dhcpToolDefinitions) toolHandlers.set(def.name, handleDhcpTool);
    for (const def of systemToolDefinitions) toolHandlers.set(def.name, handleSystemTool);
    for (const def of acmeToolDefinitions) toolHandlers.set(def.name, handleAcmeTool);
    for (const def of firmwareToolDefinitions) toolHandlers.set(def.name, handleFirmwareTool);
    for (const def of routingToolDefinitions) toolHandlers.set(def.name, handleRoutingTool);
    for (const def of vlanToolDefinitions) toolHandlers.set(def.name, handleVlanTool);
    for (const def of tailscaleToolDefinitions) toolHandlers.set(def.name, handleTailscaleTool);
    for (const def of natToolDefinitions) toolHandlers.set(def.name, handleNatTool);
Behavior2/5

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

With no annotations, the description must convey behavioral traits. It only states the action (flush cache), which implies mutation but lacks details on impact, immediacy, or side effects. Minimal disclosure.

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?

Very concise at 6 words, one sentence. Could add minor context (e.g., 'entire cache') but acceptable for a simple operation.

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

Completeness3/5

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

Adequate for a simple no-parameter action, but lacks context on side effects (e.g., performance impact) or when to use relative to siblings. No output schema, so description carries full burden.

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 schema coverage is 100% (trivially). Per guidelines, 0 params = baseline 4. Description adds no parameter info, which is acceptable.

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 specifies the action 'flush' and the resource 'Unbound DNS resolver cache'. It distinguishes from sibling tools like opnsense_dns_flush_zone (different resource) and opnsense_dns_cache_search (different action).

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_flush_zone or opnsense_dns_cache_search. No mention of when not to use or prerequisites.

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