Skip to main content
Glama
Sign In
dynadot-mcp

dynadot-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_nameserver_ip

Updates the IP addresses assigned to a registered nameserver by server ID, resolving a legacy hostname alias first when provided.

Instructions

Update IP addresses of a registered nameserver by server_id. The legacy host alias resolves an exact hostname using list_registered_nameservers before updating.

Input Schema

NameRequiredDescriptionDefault
ipNoLegacy single-address alias; use instead of ips
ipsNoReplacement addresses, encoded as ip0..ip9
hostNoLegacy hostname alias; use instead of server_id
server_idNoID from list_registered_nameservers

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.5.2
    • changedInput schema / properties / host / description
      Previous value: -"Nameserver hostname to update"New value: +"Legacy hostname alias; use instead of server_id"
    • addedInput schema / properties / host / minLength
      Added value: +1
    • addedInput schema / properties / ip / anyOf
      Added value: +[
+  {
+    "format": "ipv4"
+  },
+  {
+    "format": "ipv6"
+  }
+]
    • changedInput schema / properties / ip / description
      Previous value: -"New IP address"New value: +"Legacy single-address alias; use instead of ips"
    • addedInput schema / properties / ips
      Added value: +{
+  "description": "Replacement addresses, encoded as ip0..ip9",
+  "items": {
+    "anyOf": [
+      {
+        "format": "ipv4"
+      },
+      {
+        "format": "ipv6"
+      }
+    ],
+    "type": "string"
+  },
+  "maxItems": 10,
+  "minItems": 1,
+  "type": "array"
+}
    • addedInput schema / properties / server_id
      Added value: +{
+  "description": "ID from list_registered_nameservers",
+  "pattern": "^\\d+$",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "host",
-  "ip"
-]
  2. First observedv1.3.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses one real trait, that the host alias is resolved by exact hostname lookup before the update, but says nothing about whether the supplied addresses replace or append to existing ones, what permissions are required, or whether the change is reversible.

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, no filler. The core action is front-loaded and the alias caveat follows in second position, so a reader gets the primary contract immediately.

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 mutation tool with zero annotations and no output schema, the description covers the identifier source and the ambiguous alias behavior, which are the two genuinely confusing parts. It is still thin on the mutation's side effects (replacement vs. addition) and required authorization.

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?

Schema coverage is 100%, so every parameter is already documented, including the ip/ips and host/server_id alias relationships. The description only restates the server_id provenance and the host resolution rule, adding no format or constraint detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("Update IP addresses of a registered nameserver") and pins the identifying key ("by server_id"), which clearly separates it from siblings like register_nameserver or add_nameserver. It does not explicitly distinguish itself from set_nameservers (which targets a domain's NS set), so sibling differentiation is only partial.

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

Usage Guidelines3/5

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

It provides context for the legacy aliases ("host resolves an exact hostname using list_registered_nameservers before updating"), which implies the intended path when a caller supplies a hostname rather than an ID. However, it never states when to prefer this tool over set_nameservers or add_nameserver, nor any prerequisites such as the nameserver having to be registered first.

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

Deploy Server

Other Tools