Configure nameservers for a domain by providing a list of up to 13 hostnames.
Set nameservers for a domain. Accepts up to 13 nameserver hostnames.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name to configure | |
| nameservers | Yes | List of nameserver hostnames (e.g., ['ns1.example.com', 'ns2.example.com']) |
Changes observed during successful MCP inspections.
v1.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It does not specify whether the operation replaces existing nameservers or appends, nor does it mention authentication requirements or potential side effects. The term 'Set' is ambiguous.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise with two sentences and no wasted words. It is front-loaded with the core purpose. However, some might argue it is too terse at the expense of missing important details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool is simple with 2 parameters and no output schema, the description partially covers what is needed. But it lacks information on return format, error handling, or how it interacts with sibling tools like 'add_nameserver'.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for both parameters. The description adds no additional meaning beyond the schema; it merely restates the nameserver limit already defined in maxItems.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool sets nameservers for a domain, using the verb 'Set' and resource 'domain'. It also mentions the limit of 13 hostnames, which adds specificity. However, it does not differentiate from sibling 'add_nameserver', which may also add nameservers.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives like 'add_nameserver' or 'get_nameservers'. There is no mention of prerequisites, context, or exclusion criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.