Skip to main content
Glama

HokuHost Domains

set_nameservers

DestructiveIdempotent

Point a domain to 2–4 nameservers. Owner is emailed.

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>",
      "nameservers": "<nameservers>"
    },
    "name": "set_nameservers"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
nameserversYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds two genuine behavioral facts beyond them: the 2–4 nameserver cardinality and that the owner is emailed as a side effect. It omits the most important consequence for a destructive tool — that existing nameserver delegation is replaced — so it adds value but not full disclosure.

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?

Two short sentences with the action and the constraint front-loaded and zero filler. The sidebar about the owner email is placed after the core action, which is the right ordering, though the phrasing is telegraphic.

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

Completeness2/5

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

For a destructive, non-read-only mutation with no output schema and zero schema documentation, the description leaves out what an agent most needs: that the change overwrites prior delegation, propagation timing, and any auth/ownership requirement. Relative to its complexity the definition is thin.

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 description coverage is 0% for both parameters, so the description must compensate. It supplies a meaningful constraint the schema lacks (nameservers must number 2–4) and identifies domain as the target, but gives no format hints for either field (hostname vs IP, apex vs subdomain, duplicate handling).

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?

States a concrete verb+resource+target ("Point a domain to ... nameservers"), which is enough to distinguish it from the account/order/domain-read siblings. It stops short of naming any specific alternative, but the operation itself is unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance: nothing says whether this replaces existing nameservers or adds to them, whether the caller must own the domain, or how it relates to get_domain / renew_domain style tools. Usage must be inferred entirely from the verb.

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.

Resources