Skip to main content
Glama

Atom.com — Premium Domains

by com.atom

register_domain_spt

Destructive

Register a FRESH domain (an available domain that is NOT a curated Atom marketplace listing) by charging a Stripe Shared Payment Token (SPT) — for users with no Atom balance. This SPENDS REAL MONEY and requires the 'domains:register' scope. For already-listed marketplace domains paid from an Atom balance, use register_domain instead.

MANDATORY three-step flow — never skip a step:

  1. Call with confirm=false to get a QUOTE: price and term_years, both entirely server-authoritative (term_years is derived from the TLD; there is no such input — never invent one).

  2. Call again with confirm=true, the SAME idempotency_key, and NO payment_token: returns a structured payment_required challenge (amount, currency).

  3. Once a Shared Payment Token is obtained for that exact amount, call a third time with confirm=true, the SAME idempotency_key, and payment_token set. Payment is captured FIRST; registration only starts after that succeeds.

PAYMENT PRIORITY for a fresh registration: this tool is priority 1 — try it first, using whatever payment method your own platform can already supply for the payment_token (no external tool needed). Only if you have no way to obtain a payment_token here, fall back to priority 2: get_domain_register_pay_link, paid via link-cli's tools (e.g. mpp_pay), if those are present in this session. There is no checkout-link fallback for a fresh registration — get_checkout_link only works for an already-listed marketplace domain.

Rules: never assume or pass a price or term_years. Reuse one idempotency_key across all calls for the same intent. If registration fails AFTER payment succeeds, the registrar submission itself attempts a real refund of the charge — the result reports whether that happened. If it reports error 'registrant_contact_required', ask the user for their name, phone, address, city, zip, and country, call create_registrant_contact with those, then retry from step 1 — this is expected and not a dead end.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesThe domain to register, including extension.
confirmNofalse returns a quote; true attempts payment + registration.
payment_tokenNoShared Payment Token authorizing the exact quoted amount. Omit to receive the payment_required challenge.
idempotency_keyYesClient-generated unique key; identical across all calls for the same intended registration.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
priceNo
stageYes
domainYes
successYes
currencyNo
challengeNoPresent when stage=payment_required.
term_yearsNo
idempotency_keyNo
payment_intent_idNo
registrar_domain_idNo

TDQS

A5/5.0
Behavior5/5

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

Annotations only indicate destructive and open-world behavior, so the description carries the burden of disclosure. It goes well beyond: it warns 'SPENDS REAL MONEY', states the required 'domains:register' scope, explains the mandatory three-step protocol, clarifies that payment is captured before registration starts, discloses the refund attempt after a post-payment failure, and documents the expected registrant_contact_required 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 highly structured: purpose first, then the mandatory three-step flow, then payment priority, then rules and error handling. Every sentence carries critical operational information, and no filler or repetitive schema restating exists.

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 covers the multi-call protocol, payment priority, authentication scope, refund behavior, and a known error recovery flow. The output schema handles return-value documentation, so the description does not need to restate that, and the remaining gaps are negligible.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds substantial meaning beyond the schema: never pass price or term_years, reuse one idempotency_key across all calls, omit payment_token on the second call to get the challenge, and pass it only on the final call. These are operational semantics that the schema cannot express.

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: 'Register a FRESH domain' via a Stripe Shared Payment Token for users with no Atom balance. It explicitly distinguishes itself from register_domain, which handles already-listed marketplace domains paid from an Atom balance. This gives an agent a clear basis for selecting this tool over siblings.

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 provides explicit when-to-use and when-not-to-use guidance. It names register_domain as the alternative for marketplace domains, names get_domain_register_pay_link as the priority 2 fallback, and explicitly states that get_checkout_link does not apply to fresh registrations. This is exemplary 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