mcp-namecheap

namecheap_get_nameservers

Retrieve current nameservers for a domain and determine if it uses Namecheap DNS or custom nameservers.

Instructions

Get current nameservers for a domain and whether it uses Namecheap DNS or custom nameservers.

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

Input Schema

Name	Required	Description	Default
`domain`	Yes	Domain name (e.g. "example.com")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the transparency burden. It discloses the output behavior (returns nameservers and indicates whether Namecheap or custom DNS is used) but does not mention prerequisites, potential errors, or explicitly confirm that the operation is read-only. For a simple get tool, this is adequate but not rich.

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 sentence that leads with the action and directly conveys both the primary purpose and an additional feature. Every word contributes value, with no unnecessary elaboration.

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

Completeness4/5

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

Given the tool's simplicity (one parameter, no output schema), the description adequately captures its functionality and return information. However, it lacks explicit mention of prerequisites such as domain ownership or account authentication, and does not indicate the response format, which would improve 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?

Schema description coverage is 100% because the 'domain' parameter is already described with an example. The tool description adds no additional semantic detail for the parameter beyond what the schema provides, so the baseline of 3 applies.

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

Purpose5/5

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

The description clearly states the action 'Get' and the specific resource 'current nameservers for a domain'. It also adds a distinguishing detail about determining whether Namecheap DNS or custom nameservers are used, which differentiates it from sibling tools like namecheap_set_nameservers or namecheap_get_dns_hosts.

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?

The description implies the use case (obtaining current nameservers) but does not explicitly state when to use this tool over alternatives or include any exclusions. There is no mention of when not to use it or why one might choose namecheap_get_dns_hosts instead.

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

Deploy Server