Skip to main content
Glama
uglyswap

internetbs-mcp

by uglyswap

domain_create

Register a new domain name. Provide the domain and optional contact information, nameservers, and registration settings such as auto-renewal and WHOIS privacy.

Instructions

Register a new domain name. Requires the domain name and optionally contact information, nameservers, and registration settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesThe domain name to register (e.g. example.com)
periodNoRegistration period (e.g. 1Y for 1 year, 2Y for 2 years). Defaults to 1Y.
ns_listNoComma-separated list of nameservers (e.g. ns1.example.com,ns2.example.com)
autoRenewNoEnable or disable auto-renewal for this domain. Defaults to YES.
admin_emailNoAdmin contact email address
discountCodeNoDiscount/promo code to apply to the registration
privateWhoisNoWHOIS privacy level. FULL hides all info, PARTIAL hides some, DISABLED shows all.
billing_emailNoBilling contact email address
registrarLockNoRegistrar lock status to prevent unauthorized transfers. Defaults to ENABLED.
admin_lastnameNoAdmin contact last name
admin_firstnameNoAdmin contact first name
registrant_cityNoRegistrant city
technical_emailNoTechnical contact email address
billing_lastnameNoBilling contact last name
registrant_emailNoRegistrant email address
billing_firstnameNoBilling contact first name
registrant_streetNoRegistrant street address
technical_lastnameNoTechnical contact last name
registrant_lastnameNoRegistrant last name
technical_firstnameNoTechnical contact first name
registrant_firstnameNoRegistrant first name
registrant_postalcodeNoRegistrant postal code
registrant_countrycodeNoRegistrant country code (e.g. US, FR, DE)
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 full responsibility for behavioral disclosure. It only says 'Register a new domain name' without mentioning side effects like costs, availability checks, or possible failure modes. 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?

Two sentences, front-loaded with the purpose, and no fluff. It efficiently conveys the required vs optional inputs without wasting words.

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?

For a complex tool with 26 parameters, no output schema, and no annotations, the description omits essential operational context such as checking domain availability first (sibling domain_check), potential costs, or what happens after successful registration. The schema covers parameters but not workflow or error behavior.

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 description coverage is 100%, so parameters are fully documented in the schema. The description adds a high-level grouping ('contact information, nameservers, and registration settings') but does not meaningfully enhance the parameter understanding beyond the 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?

The description states a specific verb and resource: 'Register a new domain name.' This clearly distinguishes it from siblings like domain_check, domain_renew, and domain_update.

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 provides clear context for when to use this tool (to register a new domain) and states the requirement that 'domain' is necessary, with other fields optional. It does not explicitly exclude alternatives like renewal or transfer, but the action is distinct enough.

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