mcp-namecheap

namecheap_register_domain

Register a new domain name by providing registrant contact details. Completing the purchase charges your Namecheap account and activates the domain.

Instructions

Register (purchase) a new domain name. Requires contact information as parameters. This will charge your Namecheap account.

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>",
      "firstName": "<firstName>",
      "lastName": "<lastName>",
      "address1": "<address1>",
      "city": "<city>",
      "stateProvince": "<stateProvince>",
      "postalCode": "<postalCode>",
      "country": "<country>",
      "phone": "<phone>",
      "email": "<email>"
    },
    "name": "namecheap_register_domain"
  }
}

Input Schema

Name	Required	Description
`city`	Yes	City
`email`	Yes	Contact email address
`phone`	Yes	Phone number (e.g. "+1.5555551234")
`years`	No	Registration period in years (default: 1)
`domain`	Yes	Domain name to register (e.g. "example.com")
`country`	Yes	Country code (e.g. "US", "DE")
`address1`	Yes	Street address
`lastName`	Yes	Registrant last name
`firstName`	Yes	Registrant first name
`postalCode`	Yes	Postal/ZIP code
`whoisGuard`	No	Enable WHOIS privacy (default: true)
`nameservers`	No	Optional custom nameservers
`stateProvince`	Yes	State or province

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the critical behavioral consequence: 'This will charge your Namecheap account.' It also mentions the prerequisite of contact information. It does not discuss reversibility or failure modes, but for a purchase tool the cost warning is the key behavioral trait.

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?

Two sentences, front-loaded with the action ('Register (purchase) a new domain name') followed by the charge warning. Every word earns its place; no redundancy or filler.

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?

For a 13-parameter purchase tool with no output schema, the description is minimal. It omits helpful guidance like checking domain availability first (e.g., via namecheap_check_domain) or what fields require special formats. The cost warning is valuable, but the overall contextual picture is thin given the tool's complexity.

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%, so the baseline is 3. The description adds only a categorical grouping ('contact information') which loosely maps to the required fields, but it provides no additional meaning beyond what the schema already offers.

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?

Description uses a specific verb 'Register (purchase)' and identifies the resource 'domain name', clearly distinguishing it from sibling tools like namecheap_check_domain or namecheap_list_domains. It directly states the action without tautology.

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

Usage Guidelines4/5

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

Provides clear context: the tool requires contact information and will charge the Namecheap account. This implies when to use it (after knowing the domain is available) and what to expect, but it does not explicitly name alternative tools or when-not-to-use conditions.

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

Deploy Server