Skip to main content
Glama

Transfer domain

transfer_domain
Destructive

Transfer an existing domain to Sitequest. Requires the domain's auth code (transfer key). Creates an order, charges your saved payment method, and initiates the transfer. You MUST set confirm to true.

Discovery: use get_domain_pricing (with tld arg) to see the transfer price for the domain's TLD. Get the auth code from the current registrar's control panel.

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

Input Schema

NameRequiredDescriptionDefault
domainYesFull domain name to transfer (e.g. 'example.com')
periodNoRegistration period in years (default: 1)
confirmYesMust be true to confirm this billable operation
authCodeYesThe domain's auth code / transfer key from the current registrar

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the description's real contribution is the disclosure that this creates a billable order, charges the saved payment method, and initiates an irreversible transfer — plus the enforcement of confirm=true. It omits operational prerequisites such as disabling the transfer lock, which is a notable gap for a destructive tool with a sibling dedicated to that setting.

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-loaded with the action, then the hard requirement and the discovery steps; every line is actionable. The 'You MUST set confirm to true' line partially duplicates the schema description of confirm, which is minor redundancy rather than waste.

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?

For a four-parameter mutation with no output schema, the description covers cost discovery, credential sourcing, and the confirmation gate. It could state that an order is created and tracked via get_order_status, and mention the transfer-lock prerequisite, but nothing essential for correct invocation is missing.

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%, including descriptions for domain, authCode, confirm, and period, so the schema carries most of the semantic load. The description reinforces confirm=true and the origin of authCode, but adds no format, default, or range detail beyond the schema; baseline 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 opens with a specific verb and resource ('Transfer an existing domain to Sitequest'), which cleanly separates it from register_domain (new registration) and check_domain (availability lookup). It also names the destination registrar, so the agent knows the direction of the transfer.

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?

It gives concrete preconditions and routing: run get_domain_pricing with the tld arg to learn the transfer price, and obtain the auth code from the current registrar's control panel. It does not state when *not* to use it (e.g. domains already at Sitequest, or domains whose transfer lock is still enabled via set_transfer_lock).

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.