Skip to main content
Glama

Atom.com — Premium Domains

by com.atom

get_checkout_link

Read-only

Generate a pre-filled Atom checkout URL for a chosen domain so the user can pay on Atom. Use when a user wants to BUY a domain but is not using balance registration, lacks sufficient balance, or prefers to pay per purchase (card/PayPal). This is the no-debit alternative to register_domain.

PAYMENT PRIORITY: this is priority 3, the LAST RESORT — only for buying a premium/marketplace domain, only after BOTH register_domain (Atom balance, priority 1) is insufficient AND get_domain_purchase_pay_link + link-cli (priority 2) isn't available. There is no equivalent of this tool for a fresh domain registration or an AI Tokens purchase — neither has a checkout-link fallback.

IMPORTANT: this tool only returns a link — it does NOT charge anything or complete a purchase, and the link is NOT pre-authenticated. Tell the user they must already be logged into atom.com in the browser where they open it, or they will hit a login page instead of checkout. If the domain is already sold or is a make-offer/price-on-request listing, this errors with 'not_found' or 'not_for_sale' rather than returning a link — check get_domain_details first if unsure. Returns: domain, price + currency, checkout_url (give this to the user to finish payment), and expires_at. Present the price and the checkout link; tell the user payment completes on Atom.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesThe domain to purchase, including extension.
term_yearsNoRegistration term in years, where applicable.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
priceNoPrice in USD.
domainYes
successYes
currencyNo
expires_atNoWhen the checkout link expires.
checkout_urlYesPre-filled Atom checkout URL — give this to the user to pay.

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses critical behavior beyond the readOnlyHint annotation: the tool only returns a link, does not charge or complete the purchase, and the link is not pre-authenticated. It also explains error behavior for sold or make-offer/price-on-request domains. This materially helps the agent set user expectations and handle failures. The description is consistent with annotations.

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 every section earns its place: primary purpose, usage priority, non-debit behavior, authentication caveat, error cases, and return values. The information is front-loaded and organized with clear signposts like PAYMENT PRIORITY and IMPORTANT. The length is justified by the tool's complexity and the large sibling set.

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 role as a last-resort payment fallback with many sibling tools, the description is complete. It covers when to use it, what it returns, what it does not do, the login requirement, and likely errors. An agent has enough context to invoke this tool correctly and communicate the result to the user.

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 already documents both parameters. The description does not add much parameter-specific meaning beyond what the schema provides for domain and term_years. It reinforces the overall purchase context but does not deepen understanding of the individual parameters.

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 specifies a clear verb and resource: generate a pre-filled Atom checkout URL for a chosen domain. It explicitly differentiates itself from register_domain as the no-debit alternative and clarifies its scope to premium/marketplace purchases. This makes it easy for an agent to distinguish from the many sibling tools.

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 and when-not-to-use guidance: it is priority 3, last resort, only after register_domain and get_domain_purchase_pay_link + link-cli are unavailable. It also states there is no equivalent fallback for fresh registrations or AI Tokens purchases, and advises checking get_domain_details first when uncertain. This is unusually complete routing guidance.

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 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.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.

Resources