Skip to main content
Glama
rosschurchill

Technitium MCP Secure

dns_enable_zone

Re-enable a disabled DNS zone on your Technitium DNS server by specifying the zone domain name.

Instructions

Enable a disabled DNS zone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoneYesZone domain name to enable

Implementation Reference

  • The handler function for the dns_enable_zone tool. Validates the zone domain, calls the API endpoint /api/zones/enable, and returns a success response with the enabled zone name.
    handler: async (args) => {
      const zone = validateDomain(args.zone as string);
      const data = await client.callOrThrow("/api/zones/enable", { zone });
      return JSON.stringify(
        { success: true, enabled: zone, ...data },
        null,
        2
      );
    },
  • The schema/definition for dns_enable_zone. Includes name 'dns_enable_zone', description, and input schema requiring a 'zone' string parameter.
    definition: {
      name: "dns_enable_zone",
      description: "Enable a disabled DNS zone.",
      inputSchema: {
        type: "object",
        properties: {
          zone: {
            type: "string",
            description: "Zone domain name to enable",
          },
        },
        required: ["zone"],
      },
    },
  • The getAllTools function that aggregates all tool lists including zoneTools (which contains dns_enable_zone) and registers them together.
    export function getAllTools(client: TechnitiumClient): ToolEntry[] {
      return [
        ...dashboardTools(client),
        ...dnsClientTools(client),
        ...zoneTools(client),
        ...recordTools(client),
        ...blockingTools(client),
        ...cacheTools(client),
        ...settingsTools(client),
        ...logTools(client),
        ...appTools(client),
        ...dnssecTools(client),
      ];
    }
  • src/index.ts:21-35 (registration)
    The main server setup that calls getAllTools and builds a toolMap used to dispatch tool calls. This is where dns_enable_zone gets registered into the MCP server.
    const allTools = getAllTools(client);
    
    // Filter out write tools in readonly mode
    const tools = config.readonly
      ? allTools.filter((t) => t.readonly)
      : allTools;
    
    if (config.readonly) {
      audit.logSecurity(
        "readonly_mode",
        `Exposing ${tools.length} of ${allTools.length} tools (write tools hidden)`
      );
    }
    
    const toolMap = new Map(tools.map((t) => [t.definition.name, t]));
  • The validateDomain helper function used by the handler to validate and normalize the zone domain name.
    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;
    }
Behavior3/5

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

The description discloses that the tool enables a disabled zone, implying a state change. However, it does not detail any side effects, required permissions, or behavior when the zone is already enabled. Without annotations, the description offers minimal but adequate transparency for a simple enable operation.

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 a single, front-loaded sentence with no wasted words. Every word is essential, making it highly efficient.

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?

For a simple tool with one parameter, no output schema, and no annotations, the description is minimally adequate. However, it could be improved by noting that the zone must exist and be disabled, or by mentioning related tools like dns_disable_zone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 100% coverage with one parameter described as 'Zone domain name to enable'. The description adds no additional meaning beyond the schema, which already clearly documents the parameter.

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 'Enable' and the resource 'disabled DNS zone', directly indicating the tool's action. It distinguishes itself from sibling tools like dns_disable_zone by specifying the opposite operation.

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?

The description provides no guidance on when to use this tool versus alternatives, such as citing prerequisites or contrasting with dns_disable_zone or dns_create_zone. It lacks any contextual usage advice.

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