Atom.com — Premium Domains

Register domain via Stripe SPT

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:

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).
Call again with confirm=true, the SAME idempotency_key, and NO payment_token: returns a structured payment_required challenge (amount, currency).
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

Name	Required	Description
`domain`	Yes	The domain to register, including extension.
`confirm`	No	false returns a quote; true attempts payment + registration.
`payment_token`	No	Shared Payment Token authorizing the exact quoted amount. Omit to receive the payment_required challenge.
`idempotency_key`	Yes	Client-generated unique key; identical across all calls for the same intended registration.

Output Schema

Name	Required	Description
`url`	Yes
`price`	No
`stage`	Yes
`domain`	Yes
`success`	Yes
`currency`	No
`challenge`	No	Present when stage=payment_required.
`term_years`	No
`idempotency_key`	No
`payment_intent_id`	No
`registrar_domain_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedAug 31, 2026
RemovedAug 28, 2026
AddedAug 6, 2026
RemovedAug 5, 2026
AddedAug 4, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds critical context beyond them: it spends real money, requires the 'domains:register' scope, mandates a three-step payment flow, captures payment before registration, attempts a refund on post-payment failure, and explains the 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but front-loads purpose and exclusions, then structures the mandatory flow as a numbered sequence, which is appropriate for a high-stakes payment tool. There is some repetition around idempotency keys and fallbacks, but the length is largely justified by the complexity.

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 destructive, open-world, multi-step payment behavior, the description covers purpose, workflow, payment priority, fallback routing, idempotency, refund behavior, and error recovery. With an output schema present, it does not need to explain return values, and nothing essential for correct invocation is missing.

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?

Schema coverage is 100%, so the schema already documents each parameter. The description adds meaningful constraints beyond the schema, notably that term_years and price are server-authoritative and must never be passed, and that the same idempotency_key must be reused across the three calls, though some of this repeats schema wording.

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: registering a FRESH domain via Stripe SPT. It explicitly distinguishes this from register_domain for already-listed marketplace domains and from get_checkout_link, so an agent can select the correct 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?

It gives explicit when-to-use conditions: available domain not a curated listing, user with no Atom balance, and payment via Stripe SPT. It also names alternatives and fallbacks, including register_domain, get_domain_register_pay_link, and get_checkout_link limitations.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.