Skip to main content
Glama
rosschurchill

Technitium MCP Secure

dns_create_zone

Create a DNS zone for hosting records locally (Primary) or conditional forwarding (Forwarder).

Instructions

Create a new DNS zone. Use 'Primary' for hosting records locally, 'Forwarder' for conditional forwarding.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoneYesZone domain name (e.g. example.com)
typeNoZone type (default: Primary)

Implementation Reference

  • The handler function for dns_create_zone. Validates the domain name, optionally validates zone type (defaults to 'Primary'), and calls POST /api/zones/create on the Technitium server.
    handler: async (args) => {
      const zone = validateDomain(args.zone as string);
      const type = args.type
        ? validateZoneType(args.type as string)
        : "Primary";
      const data = await client.callOrThrow("/api/zones/create", {
        zone,
        type,
      });
      return JSON.stringify(data, null, 2);
    },
  • Input schema for dns_create_zone. Accepts 'zone' (string, required) and 'type' (enum: Primary/Secondary/Stub/Forwarder, optional).
    inputSchema: {
      type: "object",
      properties: {
        zone: {
          type: "string",
          description: "Zone domain name (e.g. example.com)",
        },
        type: {
          type: "string",
          enum: ["Primary", "Secondary", "Stub", "Forwarder"],
          description: "Zone type (default: Primary)",
        },
      },
      required: ["zone"],
    },
  • The zoneTools function is called inside getAllTools(), which collects all tool entries including dns_create_zone.
    export function getAllTools(client: TechnitiumClient): ToolEntry[] {
      return [
        ...dashboardTools(client),
        ...dnsClientTools(client),
        ...zoneTools(client),
  • src/index.ts:21-26 (registration)
    getAllTools() is invoked and tools are placed into toolMap for dispatch via CallToolRequestSchema handler.
    const allTools = getAllTools(client);
    
    // Filter out write tools in readonly mode
    const tools = config.readonly
      ? allTools.filter((t) => t.readonly)
      : allTools;
  • validateDomain() helper used by the handler to sanitize 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;
    }
  • validateZoneType() helper used by the handler to validate the zone type parameter.
    export function validateZoneType(type: string): string {
      if (!VALID_ZONE_TYPES.has(type)) {
        throw new Error(`Invalid zone type: ${type}`);
      }
      return type;
    }
  • Rate limit registration for dns_create_zone — it gets 10 requests per 60s window (mutateLimits).
    for (const tool of [
      "dns_create_zone", "dns_add_record", "dns_update_record",
      "dns_block_domain", "dns_allow_domain",
      "dns_remove_allowed", "dns_remove_blocked", "dns_delete_cached",
      "dns_enable_zone", "dns_disable_zone", "dns_set_zone_options",
      "dns_set_settings", "dns_install_app",
    ]) {
      this.toolLimits.set(tool, mutateLimits);
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'Create a new DNS zone,' implying mutation but giving no details on side effects, permissions, rate limits, or reversibility. This is insufficient for a creation tool.

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 are front-loaded: first states purpose, second adds parameter guidance. No redundant or wasted words. Achieves high density of useful information.

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 the tool's simplicity (2 params, no output schema, no nested objects), the description covers core functionality and provides type guidance. However, it omits edge cases (e.g., Secondary, Stub types) and does not explain return values or prerequisites, leaving some incompleteness.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining the meaning of the 'type' parameter (Primary vs Forwarder usage), which goes beyond schema enum labels. The 'zone' parameter is not further enhanced.

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?

Description clearly states 'Create a new DNS zone' as verb+resource, and distinguishes itself from sibling tools like dns_delete_zone and dns_list_zones. The mention of specific types (Primary, Forwarder) adds specificity.

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?

Provides explicit guidance on when to use each zone type ('Primary for hosting records locally, Forwarder for conditional forwarding'). However, it does not advise on when not to use this tool or mention alternatives, leaving a minor gap.

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