Atom.com — Premium Domains

Get website status

get_website_status

Read-onlyIdempotent

Check a website started with create_website or a logo started with regenerate_website_logo. Each call waits up to about 10 seconds, so it is safe to call back-to-back. Keep calling while stop_polling is false.

stage is one of: 'building', 'connecting' (published, domain and SSL being set up), 'live' (give the user live_url), 'private_preview' (ready; only the owner can open preview_url), 'needs_attention' (show message: the owner finishes in the editor), 'failed' (show message; create_website can be retried unless declined is set), or 'not_found'. sections lists what the site contains, so you can tell the user what was left out and that edit_url is where to add it.

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": "get_website_status"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	The domain passed to create_website.
`wait_seconds`	No	How long the server may wait while building.

Output Schema

Name	Required	Description
`url`	Yes
`stage`	Yes
`domain`	Yes
`message`	No
`success`	Yes
`declined`	No
`edit_url`	No
`live_url`	No
`logo_url`	No
`sections`	No
`published`	No
`logo_state`	No	updating, done or failed, after regenerate_website_logo.
`preview_url`	No
`stop_polling`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the ~10 second server-side wait, the safety of repeated calls, and the stop_polling termination signal. It also maps every stage value to the agent's next action (surface live_url, show message, retry create_website), which is behavior the annotations cannot express.

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 the trigger and polling rule before the stage enumeration, and nearly every clause carries actionable meaning. The stage list is long but each entry has a distinct follow-up instruction, so it earns its length; only mild density cost.

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?

An output schema exists, yet the description still explains the semantics of the stage and sections fields an agent must interpret to respond correctly, including failure and recovery paths. Nothing needed to call 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.

Parameters3/5

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

Schema coverage is 100%, with both domain and wait_seconds already documented, including bounds. The description adds only indirect context ('waits up to about 10 seconds'), which mostly restates the default rather than explaining domain format or edge cases, so baseline 3 applies.

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 a website') and immediately scopes it to artifacts produced by named siblings, create_website and regenerate_website_logo. An agent can distinguish it from the many domain/payment siblings without opening a 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 an explicit trigger (after create_website or regenerate_website_logo) and an explicit loop condition ('Keep calling while stop_polling is false'), plus reassurance that back-to-back calls are safe. This is exactly the when-and-how-often guidance a polling tool needs.

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.