Create a nameserver entry by specifying a hostname and IP address to manage DNS records for your domains.
Add (create) a new nameserver entry with a hostname and IP address.
| Name | Required | Description | Default |
|---|---|---|---|
| ip | Yes | IP address for the nameserver | |
| host | Yes | Nameserver hostname (e.g., 'ns1.example.com') |
Changes observed during successful MCP inspections.
v1.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description bears the full burden of disclosing behavior. It only states 'add (create)' implying mutation, but does not mention any side effects, validation rules, or whether duplicates are allowed. No behavioral details beyond the basic operation.
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?
A single, efficient sentence that conveys the core purpose without any superfluous words. Excellent conciseness.
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?
For a simple creation tool with two parameters and no output schema, the description is minimally adequate. However, it could be improved by mentioning expected return values or success indicators.
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 clear descriptions for both 'host' and 'ip'. The description adds no additional information beyond what the schema already provides, so baseline score applies.
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 uses a specific verb 'Add (create)' and clearly identifies the resource as a 'nameserver entry' with required fields hostname and IP address. This clearly distinguishes it from sibling tools like 'delete_nameserver' or 'set_nameserver_ip'.
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 such as 'register_nameserver' or 'set_nameserver_ip'. The description lacks context about prerequisites or conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.