Skip to main content
Glama

Transfer Domain

transfer_domain

Transfer a domain from another registrar to Spaceship. Provide the auth code to initiate the paid transfer, which includes a one-year renewal and returns an operation ID.

Instructions

Transfer a domain TO Spaceship from another registrar. WARNING: This is a FINANCIAL operation that will charge money to the Spaceship account (transfers typically include a 1-year renewal). The transfer process: 1) Unlock the domain at the current registrar, 2) Get the auth/EPP code from the current registrar, 3) Call this tool with the auth code, 4) Approve the transfer via email (if required by the TLD). Some TLDs (e.g. .uk) do not require an auth code. Transfers can take up to 5-7 days depending on the TLD. Always confirm with the user before calling this tool — show the domain name and explain the transfer process. This operation is asynchronous: it returns an operationId. Use get_transfer_status to check the transfer progress and get_async_operation to check the operation status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesThe domain name to transfer to Spaceship
authCodeNoAuthorization/EPP code from the current registrar. Required for most TLDs, but some (e.g. .uk) do not need one.
contactsNoDomain contacts by ID. Use save_contact first to create contacts and obtain IDs.
autoRenewNoEnable auto-renewal after transfer (default true)
privacyLevelNoPrivacy protection level: 'high' hides WHOIS info, 'public' shows it (default 'high')high
Behavior5/5

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

The description clearly discloses that this is a financial operation, asynchronous, and returns an operationId. It explains the full transfer process, including potential email approval and 5-7 day duration. This adds significant context beyond the annotations, which only indicate mutability and side effects.

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 appropriately sized for the complexity, with a clear warning first, then step-by-step process, then guidance. While it is longer than some, every sentence serves a purpose and contributes to understanding.

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?

Given the tool's complexity (5 params, nested objects, no output schema), the description covers process, prerequisites, side effects, and post-call actions. It references sibling tools (get_transfer_status, get_async_operation) for follow-up, providing a complete picture.

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

Parameters4/5

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

Schema coverage is 100%, providing solid parameter descriptions. The description adds value by explaining the authCode parameter's relevance to TLDs and instructing to use save_contact for contact IDs. It does not repeat schema details but enhances usability.

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 clearly states the tool transfers a domain to Spaceship from another registrar. It uses a specific verb ('transfer') and resource ('domain'), and distinguishes from sibling tools like register_domain and renew_domain by specifying the source and financial nature.

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?

The description provides explicit step-by-step instructions (1-4) and warns about financial implications. It mentions when auth code may not be needed and advises confirming with the user. However, it does not explicitly state when not to use this tool (e.g., if the domain is already at Spaceship).

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/BartWaardenburg/spaceship-mcp'

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