Skip to main content
Glama

MCPDomain

by io.github.danboabes

register_new_domain

Register a new domain. Returns a Stripe checkout URL for payment. After payment, domain is registered with FREE email forwarding, DNS, and AI bot monitoring. ALWAYS call check_domain_availability first. Collect first_name, last_name, email from user before calling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearsNoRegistration period in years. Default: 1. Most TLDs allow 1-10 years.
domainYesFull domain name to register, e.g. 'sweetcrumbs.com'. Must first be verified free via check_domain_availability.
registrantYesLegal registrant for the domain. Appears in WHOIS (private by default where the TLD supports it) and receives ICANN verification and renewal emails.

TDQS

A4.4/5.0
Behavior4/5

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

Without annotations, the description discloses that this tool returns a payment URL and only registers after payment, plus includes features like email forwarding and AI monitoring. It does not mention failure modes or refunds, but the payment caveat is a critical behavioral trait that is clearly stated.

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?

Three focused sentences with the key action, payment outcome, and preconditions. The use of capitalization for critical instructions is effective and the description is free of fluff.

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 complex transactional tool, the description covers the payment flow, post-payment features, and required preconditions. It could mention error handling or the one-time nature of the checkout URL, but the core decision-making information is present.

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 the schema documents all parameters thoroughly. The description adds the prerequisite to check availability and to collect specific user fields, but these are also in the schema; it does not provide new semantic details 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 clearly states 'Register a new domain' and specifies the payment flow via Stripe checkout URL. It distinguishes from sibling tools like check_domain_availability and transfer_existing_domain by focusing on new registrations.

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?

The description explicitly says 'ALWAYS call check_domain_availability first' and requires collecting first_name, last_name, and email before calling, providing clear preconditions. It implies this tool is for new registrations, not transfers or DNS configuration, setting expectations.

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

All MCPDomain toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool targets a distinct domain management action: availability checking, registration, suggestions, transfer, DNS config, email config, and status lookup. There is no meaningful overlap, even between check_domain_availability and suggest_available_domains, as the latter focuses on generating alternatives.

Naming Consistency5/5

All tools follow a consistent verb_noun naming pattern (check_, configure_, get_, register_, suggest_, transfer_). The two configure_ tools are clearly grouped by purpose and the rest use specific verbs, making the pattern predictable and readable.

Tool Count5/5

With 7 tools, the server is well-scoped for a domain management service. Each tool covers a distinct phase of the domain lifecycle without being either too sparse or overly granular.

Completeness4/5

The toolset covers the main domain lifecycle: finding, registering, transferring, configuring DNS/email, and monitoring status. Minor gaps exist, such as missing explicit renewal or deletion tools, but agents can work around these for typical scenarios.

Resources