Atom.com — Premium Domains

Get domain details

get_domain_details

Read-only

Get the full detail record for ONE specific Atom domain listing — the deep-dive after a user picks a name from search_brandable_domains or generate_domain_names, or asks to know more about a particular domain.

Returns: status, price + currency, extension_options[] (other TLDs of the name for sale, with prices), category, description, age/traffic when available, and purchase_url/details_url. If the domain is not an Atom listing, returns error "not_found" (then use check_domain_availability for registry status). Present price, key attributes, and the purchase link.

IMPORTANT: when price_on_request is true, price is null on purpose — this listing's price is deliberately undisclosed (make-offer/price-on-request). Never state or imply a price (including "$0" or "free") in that case; tell the user to contact the seller or make an offer via purchase_url. When available_for_purchase is false, the listing has already been sold — purchase_url is not usable; tell the user this domain is no longer available.

Input Schema

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

Output Schema

Name	Required	Description
`age`	No
`url`	Yes
`price`	No	Listing price in USD. null when price_on_request is true.
`domain`	Yes
`status`	No
`success`	Yes
`traffic`	No
`category`	No
`currency`	No
`description`	No
`details_url`	No	Atom details page.
`purchase_url`	No	Direct purchase link.
`price_on_request`	No	True when the price is deliberately undisclosed (make-offer/price-on-request) — never state a price in this case.
`extension_options`	No	Other TLDs of the name for sale, with prices.
`available_for_purchase`	No	False when this listing has already been sold/transferred — purchase_url is not usable in that case.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 31, 2026

addedOutput schema / properties / available_for_purchase

Added value: +{
+  "description": "False when this listing has already been sold/transferred — purchase_url is not usable in that case.",
+  "type": "boolean"
+}

Changed2 schema fields changedAug 19, 2026

changedOutput schema / properties / price / description

Previous value: -"Listing price in USD."New value: +"Listing price in USD. null when price_on_request is true."

addedOutput schema / properties / price_on_request

Added value: +{
+  "description": "True when the price is deliberately undisclosed (make-offer/price-on-request) — never state a price in this case.",
+  "type": "boolean"
+}

First observedJun 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only say readOnly/non-destructive; the description adds substantial non-obvious behavior: the not_found error condition, the price_on_request rule (price deliberately null, never imply $0 or free), and the available_for_purchase=false meaning the listing is sold and purchase_url is unusable. These are consequential business rules an agent could not infer from structured fields.

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?

Front-loaded with purpose and triggers, then return fields, then the two critical edge-case rules clearly flagged with IMPORTANT. The enumerated return-field list is somewhat redundant given an output schema exists, but the rest of the content earns its space.

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?

For a single-parameter read tool with annotations and an output schema, the description covers everything an agent needs: when to call it, what happens on failure, and how to interpret the two ambiguous result states (price_on_request, already sold). Nothing material 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% for the single 'domain' parameter, so the schema already defines it as a domain including extension. The description reinforces that lookups are for one specific Atom listing (implying exact-name precision rather than a search), which adds modest value 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?

States a specific verb and resource ('Get the full detail record for ONE specific Atom domain listing') and explicitly scopes it as the deep-dive step after search_brandable_domains or generate_domain_names. It also names check_domain_availability as the distinct path for non-Atom listings, so an agent can separate it from siblings without opening any schema.

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?

Gives explicit trigger conditions (user picks a name or asks for more about a particular domain) and an explicit negative/fallback path: if not an Atom listing, returns not_found and the agent should use check_domain_availability. Both when-to-use and when-not-to-use are covered.

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.