Skip to main content
Glama

get_nameservers

Retrieve current nameserver configurations for a domain registered with Dynadot to verify DNS settings or troubleshoot connectivity issues.

Instructions

Get the current nameservers configured for a domain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain name to query

Implementation Reference

  • The underlying service method that makes the API call to Dynadot.
    async getNameservers(domain: string): Promise<DynadotResponse> {
      return this.call("get_ns", { domain });
    }
  • The MCP tool registration and handler implementation for 'get_nameservers'.
    server.tool(
      "get_nameservers",
      "Get the current nameservers configured for a domain.",
      {
        domain: z.string().describe("Domain name to query"),
      },
      async ({ domain }) => {
        try {
          const result = await client.getNameservers(domain);
          return {
            content: [
              { type: "text" as const, text: JSON.stringify(result, null, 2) },
            ],
          };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return {
            content: [
              { type: "text" as const, text: `Failed to get nameservers: ${msg}` },
            ],
            isError: true,
          };
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Get') but does not reveal any behavioral traits such as read-only status, potential errors, rate limits, or authentication requirements. For a tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence that front-loads the core purpose without any wasted words. It is appropriately sized for a simple tool and earns its place by clearly stating what the tool does.

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?

Given the tool's low complexity (one parameter, no output schema, no annotations), the description is minimally adequate. However, it lacks details on return values, error handling, or behavioral context, which would be beneficial for an AI agent. It meets basic requirements but has clear gaps in completeness.

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?

The input schema has 100% description coverage, with the 'domain' parameter clearly documented. The description adds no additional meaning beyond the schema, such as format examples or constraints. According to the rules, with high schema coverage, the baseline score is 3, as the schema adequately handles parameter semantics.

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 clearly states the tool's purpose with a specific verb ('Get') and resource ('current nameservers configured for a domain'), making it immediately understandable. However, it does not explicitly differentiate from sibling tools like 'get_dns' or 'list_registered_nameservers', which might have overlapping functionality, preventing a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'get_dns' and 'list_registered_nameservers', there is no indication of context, prerequisites, or exclusions, leaving the agent to infer usage based on tool names alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mikusnuz/dynadot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server