Skip to main content
Glama
Sign In
namecheap-webui-mcp

namecheap-webui-mcp

by Microck
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

namecheap_domain_set_nameservers

Set the nameserver mode for a domain to Basic, Free, Premium, or Custom, and update custom nameserver values when needed.

Instructions

Set nameserver mode to Basic/Free/Premium/Custom and optionally update custom nameserver values.

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": {
      "domainName": "<domainName>",
      "mode": "<mode>"
    },
    "name": "namecheap_domain_set_nameservers"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNameYesFull domain name, for example example.com
modeYesNameserver mode to apply.
nameserversNoRequired for custom mode. Provide at least two nameserver hostnames.
headedNoRun with a visible browser window.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states 'Set nameserver mode' implying a mutation, but does not elaborate on side effects such as DNS propagation delays, potential service disruptions, required permissions, or idempotency. The description also fails to clarify that the 'nameservers' parameter is ignored for non-custom modes.

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?

The description is a single clear sentence that efficiently conveys the main action and optional parameter. It is front-loaded and avoids unnecessary words. However, it could be slightly improved by separating the mode setting and custom values into distinct clauses or sentences for clarity.

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?

Given the parameter count (4) and lack of output schema and annotations, the description is incomplete. It does not explain mode-specific constraints, error scenarios, or what the tool returns. For a mutation tool with potential side effects, more context about behavior and requirements is needed.

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% coverage with descriptions for all parameters. The description adds some context by noting that custom nameserver values are optional, but it does not explicitly tie the 'nameservers' parameter to the 'custom' mode. Overall, the description adds marginal value beyond the schema, meeting the baseline for high schema coverage.

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 verb 'Set' and the resource 'nameserver mode' with enumerated possible values (Basic/Free/Premium/Custom), and mentions the optional update of custom values. It distinguishes this tool from sibling tools like 'namecheap_domain_get_nameservers' (which retrieves) and 'namecheap_dns_set_records' (which sets DNS records). However, it does not explicitly differentiate from other mutation tools like 'namecheap_domain_set_feature'.

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 lacks guidance on when to use this tool versus alternatives. It does not mention that you should first retrieve current nameservers via the sibling tool, nor does it specify that the 'nameservers' parameter is required only for 'custom' mode. No prerequisites or context for usage are provided.

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

Deploy Server

Other Tools