Skip to main content
Glama

Set nameservers

set_nameservers
Destructive

Replace all nameservers of a domain at the registry. Use it only to move a domain's DNS to another provider or back to Sitequest; DNS records themselves are managed with add_dns_record, edit_dns_record and delete_dns_record. Once the domain points elsewhere, the records from list_dns_records are no longer served. Turn DNSSEC off with set_dnssec before moving away. Sitequest's nameservers are ns1.openprovider.nl, ns2.openprovider.be and ns3.openprovider.eu. The change can take several hours to reach all resolvers.

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": {
      "id": "<id>",
      "ns1": "<ns1>",
      "ns2": "<ns2>"
    },
    "name": "set_nameservers"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe domain ID
ns1YesHostname of the first nameserver, e.g. 'ns1.openprovider.nl'
ns2YesHostname of the second nameserver
ns3NoThird nameserver
ns4NoFourth nameserver
ns5NoFifth nameserver

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the replacement semantics are partly structured. The description still adds real value beyond them: it discloses that existing records stop being served after the move, requires DNSSEC off beforehand, and warns propagation can take hours. It does not say whether the old nameserver config is recoverable or what happens if fewer than two entries are supplied, so it falls short of full behavioral disclosure for a destructive 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?

Four sentences, zero filler, and the destructive core action is stated first. Each subsequent sentence (scope, side effect, prerequisite, propagation) earns its place.

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?

For a six-parameter destructive mutation with no output schema, the description covers scope, side effects, prerequisites, propagation delay and concrete values. Nothing needed in order to call it correctly is missing.

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 the baseline is 3, and the description goes beyond it by giving concrete hostname values for Sitequest's nameservers (ns1.openprovider.nl, ns2.openprovider.be, ns3.openprovider.eu), which directly informs what to pass for ns1–ns3. It adds no meaning for id or for ns4/ns5.

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?

States a specific verb and resource ("Replace all nameservers of a domain at the registry") and immediately distinguishes it from the record-level siblings add_dns_record, edit_dns_record and delete_dns_record. An agent can tell precisely what this tool does and does not touch.

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?

Explicitly limits use to moving a domain's DNS to another provider or back to Sitequest, and routes record-level work to the named sibling tools. It also supplies a prerequisite ordering rule (disable DNSSEC with set_dnssec first) and names the alternative for the adjacent need, which is the strongest form of guidance.

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.