Skip to main content
Glama

create_dns_zone

Idempotent

Create the DNS zone for a domain the authenticated customer already owns on AIvikings' own nameservers, so its DNS records can be managed here. Use it before adding records to an existing domain that should use AIvikings DNS, then point the domain to the returned nameservers with update_nameservers (which also creates the zone by itself). Safe to call again: an existing zone is kept. The new zone starts empty; records at the previous DNS provider are not copied, so ask the user which records the domain needs (for example its website A record and mail MX records).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "create_dns_zone"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that an existing zone is kept on repeat calls, the new zone starts empty, previous-provider records are not copied, and nameservers are returned for the next step. These are meaningful behavioral details for a write operation, and they align with the idempotent and non-destructive annotations.

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?

The description is front-loaded with the core action and then adds usage and caveats, with no filler. It is slightly long and the update_nameservers caveat is a little dense, but every sentence contributes useful operational context.

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

Completeness5/5

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

Given the existing output schema and annotations, the description covers prerequisites, sequencing with record creation, idempotency, empty-zone behavior, non-migration of records, and the next nameserver step. That is complete enough for an agent to call the tool correctly.

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 only a required 'domain' string with zero description coverage. The description adds eligibility context—the domain must be owned by the authenticated customer and on AIvikings nameservers—but it does not clarify the expected string format or whether subdomains are valid, so it only partially compensates for the schema gap.

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 states a specific action and object: creating a DNS zone for a domain the authenticated customer owns on AIvikings nameservers, so records can be managed there. It distinguishes the tool from update_nameservers by noting that update_nameservers also creates the zone by itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to use this before adding records to an existing domain that should use AIvikings DNS, points to update_nameservers for nameserver changes, and notes that update_nameservers can create the zone by itself. It also explains idempotent behavior and the need to ask the user which records are required.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.