Atom.com — Premium Domains

get_domain_register_pay_link

Read-only

Get a real, payable Machine Payment Protocol (MPP) URL to register a FRESH domain (an available domain that is NOT a curated Atom marketplace listing — for that, use get_domain_purchase_pay_link instead) via Stripe SPT — for use with an MPP-native payment agent (e.g. Stripe's link-cli), NOT with register_domain_spt's own payment flow (that tool's challenge cannot be paid by an external MPP agent). Use this ONLY when an MPP-native agent's tools (e.g. link-cli's mpp_pay) are available in this session.

PAYMENT PRIORITY: this is priority 2 for a fresh registration — reach for it only after register_domain_spt's own in-band payment flow (priority 1) isn't viable (no payment_token available from your own platform), and only when link-cli is present. Always hand over the exact server-computed pay_url/price returned here — never estimate or recompute the amount yourself. There is no checkout-link fallback for a fresh registration.

Returns a pay_url that a real HTTP 402 challenge is served from — hand it directly to the MPP agent's pay tool (e.g. mpp_pay) rather than fetching or decoding it yourself. term_years is never a caller input — always derived server-side from the TLD.

If this reports error 'registrant_contact_required' (a registry needs this to complete registration), ask the user for their name, phone, address, city, zip, and country, call create_registrant_contact with those, then retry this tool — this is expected and not a dead end.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	Yes	The domain to register, including extension.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes
`price`	No
`domain`	Yes
`pay_url`	Yes	Real MPP-payable URL — hand this to an MPP agent, do not fetch it yourself.
`success`	Yes
`currency`	No
`expires_at`	No
`term_years`	No

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and the description aligns with that. It adds valuable behavioral context beyond annotations: the returned pay_url comes from a real HTTP 402 challenge, the caller should hand it to an MPP pay tool rather than fetching/decoding it, term_years is always server-derived, and the registrant_contact_required error has a defined recovery path.

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 long but well-structured and front-loaded with the core purpose. Each section earns its place: routing to the correct sibling, payment priority, return-value handling, and error recovery. There is no filler or redundancy, and the labeled structure helps an agent parse the key constraints quickly.

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, the description is complete: it explains when to use it, what it returns, how to handle the result, and how to recover from a known error. The presence of an output schema and a single fully documented parameter lowers the burden, and the description covers all essential invocation context.

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?

The input schema already fully describes the only parameter, 'domain', with 100% coverage. The description reinforces its meaning by specifying that the domain must be fresh and available, not a curated marketplace listing, and clarifies that term_years is never a caller input. This adds contextual semantics 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 action and resource: getting a real, payable MPP URL to register a fresh domain. It explicitly contrasts with get_domain_purchase_pay_link by saying it is NOT for curated Atom marketplace listings, so an agent can distinguish it from the sibling without opening schemas.

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 gives explicit when-to-use guidance: only when MPP-native tools like link-cli's mpp_pay are available, and as priority 2 after register_domain_spt's in-band payment flow is not viable. It also names the alternative for curated listings and states there is no checkout-link fallback for fresh registrations.

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

All Atom.com — Premium Domains tools Inspect

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.1/5.0

Disambiguation2/5

Several tools serve the same resource+action through different payment channels (e.g., register_domain, register_domain_spt, get_domain_register_pay_link; purchase_domain, get_domain_purchase_pay_link, get_checkout_link; buy_ai_tokens, get_ai_tokens_pay_link). brainstorm_names is explicitly a duplicate of search_brandable_domains, so the set has multiple confusing overlaps despite detailed descriptions.

Naming Consistency4/5

Most tool names follow a predictable snake_case verb_noun pattern (appraise_domain, check_domain_availability, purchase_domain, screen_trademark_conflicts). Minor deviations like brainstorm_names, register_domain_spt, and get_checkout_link break the pattern slightly but remain readable and recognizable.

Tool Count3/5

Sixteen tools is right at the boundary where a tool set starts to feel heavy. Many tools are legitimately needed for discovery, purchasing, and payment routing, but the duplicate name-generation tool and the multiple payment-route variants add unnecessary bulk.

Completeness4/5

The core domain lifecycle is well covered: search/discovery, availability checks, details, appraisal, trademark screening, registrant contact, and both fresh registration and marketplace purchase paths are present. Minor gaps exist around post-purchase management, account balance visibility, and offer submission, but the main user journey has no significant dead ends.

get_domain_register_pay_link

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources