Skip to main content
Glama
rosschurchill

Technitium MCP Secure

dns_list_cache

List cached DNS zones hierarchically. Omit domain to see top-level zones, or specify a domain like 'com' to drill into its cached subdomains.

Instructions

List zones in the DNS cache. Returns a hierarchical tree — call with no domain to see top-level zones, then pass a domain (e.g. 'com') to drill into cached subdomains.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoOptional parent domain to list children of (e.g. 'com' to see cached .com domains). Omit to see top-level zones.

Implementation Reference

  • The handler function for dns_list_cache. Accepts an optional domain argument, validates it, calls the /api/cache/list endpoint, and returns the result as formatted JSON.
    handler: async (args) => {
      const params: Record<string, string> = {};
      if (args.domain) params.domain = validateDomain(args.domain as string);
      const data = await client.callOrThrow("/api/cache/list", params);
      return JSON.stringify(data, null, 2);
    },
  • The schema/definition for dns_list_cache. Declares the tool name, description, and inputSchema with an optional 'domain' string property.
    definition: {
      name: "dns_list_cache",
      description:
        "List zones in the DNS cache. Returns a hierarchical tree — call with no domain to see top-level zones, then pass a domain (e.g. 'com') to drill into cached subdomains.",
      inputSchema: {
        type: "object",
        properties: {
          domain: {
            type: "string",
            description:
              "Optional parent domain to list children of (e.g. 'com' to see cached .com domains). Omit to see top-level zones.",
          },
        },
      },
    },
  • src/tools/index.ts:8-8 (registration)
    Import of cacheTools (which includes dns_list_cache) into the tool index.
    import { cacheTools } from "./cache.js";
  • Registration of cacheTools (including dns_list_cache) into the getAllTools array.
    ...cacheTools(client),
  • The validateDomain helper used by the handler to validate and normalize the domain argument before passing it to the API.
    export function validateDomain(domain: string): string {
      if (!domain || typeof domain !== "string") {
        throw new Error("Domain name is required");
      }
      const trimmed = domain.trim().toLowerCase();
      if (trimmed.length > 253) {
        throw new Error("Domain name exceeds maximum length of 253 characters");
      }
      if (!DOMAIN_RE.test(trimmed)) {
        throw new Error("Invalid domain name format");
      }
      return trimmed;
    }
Behavior4/5

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

The description discloses the hierarchical tree return structure and the behavior of parameter omission vs. inclusion. While no annotations exist, it adds meaningful behavioral context beyond a simple 'list' statement.

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?

Two sentences with no wasted words. The key information is front-loaded: the action and resource are immediately clear, followed by essential usage details.

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 list tool with no output schema, the description explains the hierarchical output and parameter usage sufficiently. It could mention what the tree contains (e.g., zone names), but overall it's adequate.

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?

With 100% schema coverage, baseline is 3. The description adds value by explaining the domain parameter's purpose (optional, for drilling) and contrasting behavior when omitted vs. provided, exceeding schema alone.

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 lists zones in the DNS cache, uses a specific verb ('List zones'), and explains the hierarchical drill-down behavior, distinguishing it from sibling tools like dns_list_zones by focusing on cached zones.

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?

It provides explicit usage instructions: call without domain for top-level zones, or with a domain to drill into subdomains. It does not mention when not to use or alternatives, but the guidance is clear and actionable.

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/rosschurchill/technitium-mcp-secure'

If you have feedback or need assistance with the MCP directory API, please join our Discord server