Skip to main content
Glama
RareCloudio

@rarecloudio/mcp-server

Official
by RareCloudio

register_domain

Register a new domain name with optional WHOIS privacy, DNS management, and custom nameservers. Requires explicit user confirmation before spending from your account.

Instructions

Register a new domain name. Requires scope domains:write. SPENDS MONEY: places a register ORDER + invoice (WHMCS has no "register now" API) that the registrar fulfils once accepted/paid — the returned status starts Pending. Pass confirm:true only after the user has approved the cost. domain is the full name, e.g. example.com; years is the registration term (1-10, default 1); nameservers is an optional list of up to 5 custom nameserver hostnames (omit to use the registrar default); idProtection/dnsManagement are optional WHOIS-privacy / DNS-hosting add-ons (registrar-dependent). Check availability first with check_domain_availability and price with get_tld_pricing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearsNoRegistration term in years (1-10, default 1).
domainYesThe domain to register, e.g. example.com.
confirmYesSet to true to execute. This operation spends from your account balance and/or is irreversible; only pass true after the user has explicitly approved. Omit or false → the tool refuses and makes no API call.
nameserversNoOptional custom nameservers (up to 5); omit to use the registrar default.
idProtectionNoOptional WHOIS-privacy add-on (registrar-dependent).
dnsManagementNoOptional DNS-hosting add-on (registrar-dependent).
Behavior5/5

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

No annotations provided, so description fully handles behavioral disclosure. It states the money-spending nature, order/invoice process, initial Pending status, and confirm flag requirement. Provides rich transparency.

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?

Single paragraph is information-dense and effective, but lacks structural breaks for readability. Minor deduction.

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

Completeness5/5

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

No output schema, but description explains return status and prerequisites. Covers all aspects: prerequisites, parameters, behavior, and confirm flag. Very complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds extra context: explains domain format, years default, nameservers limit, and add-ons. Adds value beyond schema.

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 clearly states 'Register a new domain name' with specific verb+resource. It distinguishes from sibling tools like check_domain_availability and get_tld_pricing by referencing them.

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

Usage Guidelines5/5

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

Explicitly advises to check availability with check_domain_availability and price with get_tld_pricing first. Also explains when to set confirm:true, providing clear usage context.

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/RareCloudio/rarecloud-mcp-server'

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