Skip to main content
Glama

Register domain

register_domain
Destructive

Register a new domain. Creates an order, charges your saved payment method, and provisions the domain. Returns the order ID to track progress via get_order_status. You MUST set confirm to true.

Discovery: use check_domain first to confirm availability and price (incl. premium-fee detection). Use get_domain_pricing to enumerate supported TLDs and their renewal prices.

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

Input Schema

NameRequiredDescriptionDefault
domainYesFull domain name to register (e.g. 'example.com')
periodNoRegistration period in years (default: 1)
confirmYesMust be true to confirm this billable operation
nameserversNoCustom nameservers (e.g. ['ns1.example.com', 'ns2.example.com'])
whoisPrivacyNoEnable WHOIS privacy protection

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description reinforces this by disclosing the billable charge, order creation, and the mandatory confirm flag — meaningful additions. However, it doesn't cover failure/rollback behavior (e.g. what happens if provisioning fails after the charge) or whether the charge is immediate versus deferred, which is the critical remaining unknown for a paid mutation.

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?

Front-loads the effect chain, then separates discovery guidance into a labeled line, which is easy to scan. A few clauses (premium-fee parenthetical, TLD enumeration) are marginally redundant with sibling tool names but still earn their place.

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 exists, yet the description states the return value (order ID) and the tracking path via get_order_status. Combined with the confirm guardrail and discovery prerequisites, an agent has everything needed to invoke this billable operation safely.

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 coverage is 100%, so all five parameters are already documented, and the description only restates the confirm requirement without adding syntax or constraints. It says nothing about how period, nameservers, or whoisPrivacy interact with registration, leaving the schema to carry the load — baseline 3.

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?

States a specific verb and resource plus its full effect chain: creates an order, charges the saved payment method, and provisions the domain. That distinguishes it cleanly from check_domain, get_domain, and transfer_domain.

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?

Gives explicit sequencing: run check_domain first for availability and price including premium fees, use get_domain_pricing for TLD/renewal enumeration, and set confirm=true to proceed. Tracking is routed to get_order_status, so prerequisites and follow-ups are all named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.