Atom.com — Premium Domains

register_domain

Destructive

Register a FRESH domain — an available domain that is NOT an existing Atom marketplace listing — directly at the registrar. This SPENDS REAL MONEY and requires the 'domains:register' scope. Use this ONLY when check_domain_availability reported status 'available' for this exact domain. If the domain is instead an Atom marketplace listing (status 'premium'/'taken'), use purchase_domain instead — never this tool; it will reject a marketplace domain with error 'is_marketplace_listing'.

MANDATORY two-step flow — never skip the quote:

Call with confirm=false (default) to get a QUOTE: returns the authoritative price, its breakdown (unit_price, icann_total, vat_amount), term_years (server-derived from the TLD — never assume or pass one), the user's current balance, sufficient_funds, whether a saved card exists (has_saved_card / saved_card), and expires_at.
SHOW THE USER: the exact price breakdown, and state plainly which payment method you are about to use and how much it will charge — e.g. "$19.98 (domain $17.99 + ICANN fee $1.99) from your Atom balance" or "...from your saved Visa ending 4242". Get explicit confirmation before proceeding.
Call again with confirm=true, the SAME idempotency_key, and payment_method set to exactly 'balance' or 'saved_card' (REQUIRED at this step — never omit it or guess): commits the charge and the registration. Returns status='registered', amount_charged, payment_method, and registrar_domain_id — the domain now shows up in the user's Atom account (dashboard → My Domains).

Rules: never assume or pass a price. Reuse one client-generated idempotency_key across both calls (and any retry) to prevent double-charging. If it reports error 'registrant_contact_required' (a registry needs this to complete registration), call create_registrant_contact with the user's name, phone, address, city, zip, and country, then retry with confirm=true. If payment_method='balance' and funds are insufficient, error 'insufficient_funds' reports required/available/top_up_url and whether a saved card exists as an alternative — tell the user both options plainly, do not silently retry with the other method. If payment_method='saved_card' and the charge fails, error 'card_payment_failed' reports why (including if it needs 3D Secure authentication, which cannot be completed here — offer balance or a different card instead).

Input Schema

TableJSON Schema

Name	Required	Description
`domain`	Yes	The fresh domain to register, including extension.
`confirm`	No	false returns a quote; true commits the charge and registration (payment_method required).
`payment_method`	No	Which rail to charge. REQUIRED when confirm=true — state this to the user before calling, never picked automatically. Ignored (and unnecessary) at the quote stage.
`idempotency_key`	Yes	Client-generated unique key; identical across the quote and confirm calls for the same intended registration. Prevents double-charging on retry.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes
`price`	No	Authoritative total price in USD (quote stage).
`stage`	Yes	'quote' = price for confirmation; 'committed' = registration completed.
`domain`	Yes
`status`	No	Registration status (committed stage).
`balance`	No	User's current Atom balance (quote stage).
`success`	Yes
`currency`	No
`breakdown`	No	Price components (quote stage): unit_price, icann_total, vat_amount.
`next_step`	No	How to complete the registration (quote stage).
`expires_at`	No	Quote expiry (quote stage).
`saved_card`	No	{brand, last4} of the saved card, if any (quote stage).
`term_years`	No	Server-derived from the TLD.
`amount_charged`	No	Amount actually charged in USD (committed stage).
`has_saved_card`	No	Whether the user has a saved/default card on file (quote stage).
`payment_method`	No	Which rail was actually charged (committed stage).
`idempotency_key`	No
`sufficient_funds`	No	Whether balance covers the price (quote stage).
`registrar_domain_id`	No	Registrar domain id (committed stage).

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedAug 28, 2026

changedInput schema / properties / confirm / description

Previous value: -"false returns a quote for confirmation; true commits the debit and registration."New value: +"false returns a quote; true commits the charge and registration (payment_method required)."

changedInput schema / properties / domain / description

Previous value: -"The domain to register or purchase, including extension."New value: +"The fresh domain to register, including extension."

changedInput schema / properties / idempotency_key / description

Previous value: -"Client-generated unique key; identical across the quote and confirm calls for the same intended purchase. Prevents double-registration on retry."New value: +"Client-generated unique key; identical across the quote and confirm calls for the same intended registration. Prevents double-charging on retry."

addedInput schema / properties / payment_method

Added value: +{
+  "description": "Which rail to charge. REQUIRED when confirm=true — state this to the user before calling, never picked automatically. Ignored (and unnecessary) at the quote stage.",
+  "enum": [
+    "balance",
+    "saved_card"
+  ],
+  "type": "string"
+}

removedInput schema / properties / term_years

Removed value: -{
-  "default": 1,
-  "description": "Registration term in years (for registrable domains).",
-  "type": "integer"
-}

addedOutput schema / properties / amount_charged

Added value: +{
+  "description": "Amount actually charged in USD (committed stage).",
+  "type": "number"
+}

removedOutput schema / properties / amount_debited

Removed value: -{
-  "description": "Amount charged in USD (committed stage).",
-  "type": "number"
-}

addedOutput schema / properties / balance

Added value: +{
+  "description": "User's current Atom balance (quote stage).",
+  "type": [
+    "number",
+    "null"
+  ]
+}

removedOutput schema / properties / balance_after

Removed value: -{
-  "description": "Projected balance after purchase (quote stage).",
-  "type": [
-    "number",
-    "null"
-  ]
-}

removedOutput schema / properties / balance_remaining

Removed value: -{
-  "description": "Remaining balance (committed stage).",
-  "type": [
-    "number",
-    "null"
-  ]
-}

addedOutput schema / properties / breakdown

Added value: +{
+  "description": "Price components (quote stage): unit_price, icann_total, vat_amount.",
+  "type": "object"
+}

addedOutput schema / properties / has_saved_card

Added value: +{
+  "description": "Whether the user has a saved/default card on file (quote stage).",
+  "type": "boolean"
+}

changedOutput schema / properties / next_step / description

Previous value: -"How to complete the purchase (quote stage)."New value: +"How to complete the registration (quote stage)."

removedOutput schema / properties / order_id

Removed value: -{
-  "description": "Atom order id (committed stage).",
-  "type": [
-    "string",
-    "number",
-    "null"
-  ]
-}

addedOutput schema / properties / payment_method

Added value: +{
+  "description": "Which rail was actually charged (committed stage).",
+  "enum": [
+    "balance",
+    "saved_card"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / price / description

Previous value: -"Authoritative price in USD (quote stage)."New value: +"Authoritative total price in USD (quote stage)."

addedOutput schema / properties / registrar_domain_id

Added value: +{
+  "description": "Registrar domain id (committed stage).",
+  "type": [
+    "string",
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / saved_card

Added value: +{
+  "description": "{brand, last4} of the saved card, if any (quote stage).",
+  "type": "object"
+}

changedOutput schema / properties / stage / description

Previous value: -"'quote' = price for confirmation; 'committed' = purchase completed."New value: +"'quote' = price for confirmation; 'committed' = registration completed."

addedOutput schema / properties / term_years / description
```
Added value: +"Server-derived from the TLD."
```

AddedAug 6, 2026
RemovedAug 5, 2026
AddedAug 4, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the annotations (destructiveHint, openWorldHint), the description discloses that the tool 'SPENDS REAL MONEY', requires the 'domains:register' scope, follows a mandatory quote-then-confirm flow, reuses an idempotency key to prevent double-charging, and surfaces specific error behaviors (insufficient_funds, card_payment_failed, is_marketplace_listing). This is far beyond what annotations alone convey.

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 sentence carries essential operational guidance for a high-stakes, two-step payment tool. It is structured with a numbered three-step flow, explicit rules, and error-handling notes, all front-loaded after a purpose statement. No filler or repetition; the density is justified by the tool's 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?

The description covers prerequisites, the exact invocation sequence, required user consent messaging, payment method selection, idempotency, error recovery paths, and post-condition (domain appears in My Domains). With an output schema present, no return-format explanation is needed. Given the tool's complexity and the rich sibling set, this is fully complete.

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%, but the description adds substantial meaning: confirm=false produces a quote, confirm=true commits the charge, payment_method is required only at confirmation and must be exactly 'balance' or 'saved_card', and the idempotency_key must be identical across both calls. It also clarifies that term_years is server-derived and should never be passed, enriching parameter understanding 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 verb and resource: 'Register a FRESH domain' directly at the registrar, and explicitly distinguishes a fresh, available domain from an Atom marketplace listing. It also names the sibling purchase_domain as the alternative for marketplace domains, making the tool's unique scope unmistakable.

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 an explicit condition: use this ONLY when check_domain_availability reported status 'available' for the exact domain. It also specifies when NOT to use it (status 'premium'/'taken' → use purchase_domain) and how to recover from the 'registrant_contact_required' error by calling create_registrant_contact. Alternatives and exclusions are fully spelled out.

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.