Skip to main content
Glama

Atom.com — Premium Domains

Check domain availability

check_domain_availability
Read-only

Check whether ONE specific, fully-spelled domain is available, taken, or a premium listing. Use whenever a user names a specific domain (e.g. "is acme.com available?", "who owns x.io?", "can I get nova.ai?"). For open-ended "suggest names for my idea" requests use search_brandable_domains instead. If the user wants to PURCHASE a domain they already know is an Atom marketplace listing, use get_domain_details instead — this tool checks fresh-registration availability, which will misleadingly report an already-listed/owned domain as "taken."

Returns: status ("available" = registrable now | "taken" = registered/unavailable | "premium" = for sale on Atom), registrable (bool), price + currency when applicable, estimated_value (rough appraisal, optional), and alternatives[] — when the domain is taken or premium, the closest available premium names from Atom (each with domain, price, url) so the user always has a buyable path.

IMPORTANT — which tool to call next depends on status, and the top-level url means different things accordingly: status "available" (a fresh domain, NOT an Atom marketplace listing) → call register_domain to register it directly in this conversation; its url is a self-service registration page on Atom, only worth mentioning if the user prefers to do it themselves. Status "taken" or "premium" (an existing Atom marketplace listing) → call purchase_domain to buy it directly in this conversation; its url is the marketplace listing page. Never call register_domain for a "premium"/"taken" domain or purchase_domain for an "available" one — each rejects the wrong case with a clear error. Both tools quote a real price breakdown and ask you to state the payment method (Atom balance or saved card) before charging anything. If register_domain reports error registrant_contact_required, that's expected for a fresh domain and not a dead end: ask the user for their name, phone, address, city, zip, and country, call create_registrant_contact with those, then retry register_domain with confirm=true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "check_domain_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe domain to check, including extension, e.g. 'example.com'.

Output Schema

NameRequiredDescriptionDefault
urlYesAtom URL for this domain.
priceNoPrice in USD when applicable. Null for make-offer/price-on-request listings.
domainYes
statusYesavailable = registrable now; taken = registered/unavailable; premium = for sale on Atom.
successYes
currencyNo
registrableYesWhether the domain can be registered now.
alternativesNoClosest available Atom premium names when the domain is taken/premium.
estimated_valueNoRough appraisal in USD (optional).
price_on_requestNoTrue when the listing price is deliberately undisclosed (make-offer/price-on-request). Do not state or estimate a price; point the user to the listing to make an offer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / price / description
      Previous value: -"Price in USD when applicable."New value: +"Price in USD when applicable. Null for make-offer/price-on-request listings."
    • addedOutput schema / properties / price_on_request
      Added value: +{
      +  "description": "True when the listing price is deliberately undisclosed (make-offer/price-on-request). Do not state or estimate a price; point the user to the listing to make an offer.",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / alternatives / items / properties / logo
      Added value: +{
      +  "description": "Listing logo image URL.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, but the description adds substantial context: the three status values and their meanings, that a listed domain can be misleadingly reported as "taken", that url means different things per status, and the expected registrant_contact_required error path. The only gap is that the return field descriptions overlap with what an output schema may already convey.

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?

Dense but well ordered: purpose and trigger, then exclusions, then return shape, then next-tool routing. The closing registrant_contact_required recovery paragraph is arguably register_domain's concern and makes the block long, but it is actionable rather than filler and nothing is front-loaded badly.

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?

Despite being a one-parameter read tool, it fully covers the complexity that matters: what each status means, what comes back (alternatives, price, estimated_value), and which sibling to call next in each case. Nothing an agent needs to invoke or act on the result 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 baseline is 3, but the description adds meaning beyond the schema: exactly ONE domain per call, must be fully spelled, and examples of natural-language user phrasings that map to the single parameter. That is a real constraint not captured by the schema's "including extension" note.

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 ("Check whether ONE specific, fully-spelled domain is available, taken, or a premium listing") and immediately names the two sibling tools it is not (search_brandable_domains, get_domain_details). An agent can distinguish it from the other 20 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 with quoted user phrasings, plus negative routing: open-ended naming requests go to search_brandable_domains, known marketplace listings go to get_domain_details. It also spells out the downstream branching by status, which is the real decision an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.