Skip to main content
Glama
uglyswap

internetbs-mcp

by uglyswap

transfer_initiate

Initiate a domain transfer to your Internet.bs account by providing the domain name and optional EPP auth code, nameservers, registrant contact, and transfer options.

Instructions

Initiate a domain transfer to your Internet.bs account. Requires the domain name and optionally the EPP auth code, registration period, registrant contact info, nameservers, and other transfer options.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesThe domain name to transfer (e.g. example.com)
periodNoRegistration period (e.g. '1Y' for 1 year)
ns_listNoComma-separated list of nameservers (e.g. 'ns1.example.com,ns2.example.com')
privateWhoisNoPrivate WHOIS setting: FULL, PARTIAL, or DISABLED
registrarLockNoRegistrar lock setting: ENABLED or DISABLED
registrant_cityNoRegistrant city
registrant_emailNoRegistrant email address
transferAuthInfoNoThe EPP authorization/transfer code from the current registrar
registrant_streetNoRegistrant street address
registrant_lastnameNoRegistrant last name
registrant_firstnameNoRegistrant first name
registrant_postalcodeNoRegistrant postal/zip code
registrant_countrycodeNoRegistrant country code (e.g. US, FR)
registrant_phonenumberNoRegistrant phone number (e.g. +1.5551234567)
cloneContactsFromDomainNoClone contact information from an existing domain in your account
registrant_organizationNoRegistrant organization
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the action and lists optional parameters, failing to disclose important behavioral aspects such as fees, transfer duration, potential failure conditions, or whether an EPP code is mandatory. This is a significant gap for a mutation tool.

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?

The description is a single sentence that front-loads the core purpose and efficiently summarizes optional inputs. There is no filler or redundancy.

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

Completeness2/5

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

Given the tool's complexity (16 params, no annotations, no output schema), the description is too sparse. It does not mention expected outcomes, prerequisites (like domain unlock), or any post-transfer behavior, leaving the agent without enough context to fully understand the operation.

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?

The schema already describes all 16 parameters with 100% coverage. The description groups parameters into categories ('EPP auth code, registration period, registrant contact info') but adds no new semantic detail beyond what the schema provides.

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 uses the specific verb 'Initiate' with the resource 'domain transfer' and directs it 'to your Internet.bs account.' This clearly distinguishes the tool from sibling transfer-management tools like transfer_cancel, transfer_history, and transfer_retry.

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

Usage Guidelines3/5

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

The description implies this tool is used to start a domain transfer, but it does not explicitly state when to use it versus other transfer tools or mention any exclusions or alternatives. Usage context is present but not explicit.

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/uglyswap/internetbs-mcp'

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