Skip to main content
Glama
itunified-io

mcp-opnsense

by itunified-io

opnsense_dns_list_blocklist

Lists all domain overrides configured for domain blocking in Unbound DNS resolver. Retrieve current blocklist entries to verify or audit DNS filtering rules.

Instructions

List all domain overrides (used for domain blocking) in Unbound

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for opnsense_dns_list_blocklist. Calls /unbound/settings/searchDot API endpoint (since OPNsense 24.7+ merged domain overrides into dots model) and returns the result as JSON.
    case "opnsense_dns_list_blocklist": {
      // OPNsense 24.7+: domain overrides merged into dots model
      const result = await client.get("/unbound/settings/searchDot");
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • Tool definition/registration for opnsense_dns_list_blocklist in the dnsToolDefinitions array. Defines name, description, and inputSchema (no params needed).
    {
      name: "opnsense_dns_list_blocklist",
      description: "List all domain overrides (used for domain blocking) in Unbound",
      inputSchema: { type: "object" as const, properties: {} },
    },
  • src/index.ts:59-59 (registration)
    Registers all DNS tools (including opnsense_dns_list_blocklist) by mapping their names to the handleDnsTool function in the toolHandlers Map.
    for (const def of dnsToolDefinitions) toolHandlers.set(def.name, handleDnsTool);
Behavior3/5

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

No annotations provided. The description implies a read operation ('List') but does not explicitly state it is non-destructive or safe. It does not disclose any behavioral traits beyond the basic action.

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 with no extraneous words. The purpose is front-loaded and clear.

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?

Given no parameters or output schema, the description is minimal. It does not explain what information is returned (e.g., names only or full details). Adequate for a simple list tool but could be more informative.

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%. The description adds no parameter info, but with zero parameters, baseline is 4.

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 explicitly states 'List all domain overrides (used for domain blocking)' which clearly specifies the verb (list), resource (domain overrides), and purpose (blocking). It distinguishes from sibling tool opnsense_dns_list_overrides implying a filtered subset.

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 vs alternatives like opnsense_dns_list_overrides or opnsense_dns_blocklist_get. The description lacks any context about prerequisites or scenarios.

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