Atom.com — Premium Domains

Get Coinbase payment status

get_coinbase_payment_status

Read-onlyIdempotent

Check a Coinbase (USDC) payment created by get_domain_purchase_coinbase_pay_link, get_domain_register_coinbase_pay_link or get_add_funds_coinbase_pay_link, and complete the purchase / registration / funds credit once it is paid. Each call waits up to ~10 seconds server-side and re-checks before answering, so it is safe to call back-to-back.

POLLING: right after handing over the pay link (or after an x402 wallet pays it), keep calling this while status is 'pending' and stop_polling is false — no need to wait between calls. When stop_polling is true (about 15 minutes after the link was created), STOP polling and show the returned user_message to the user exactly as given (it is a highlighted warning). When the user later says they have paid, call this again.

status is one of: 'pending' (not confirmed yet), 'completed' (domain purchased / funds credited — tell the user), 'failed' (checkout expired or failed, nothing captured — offer a new link), 'refunded' (paid, but the registry rejected the registration — the amount was credited to the Atom account balance), or 'needs_support' (paid but could not be applied automatically — give the user the message as-is).

Input Schema

Name	Required	Description	Default
`payment_code`	Yes	payment_code returned by the Coinbase pay-link tool.
`wait_seconds`	No	How long the server may wait for the payment before answering (default 10). Use 0 for an instant check.

Output Schema

Name	Required	Description
`url`	No	Where the user can see the result: My Domains (/dashboard/registrar) for a registration or marketplace purchase, the Atom dashboard (/dashboard) for add funds.
`type`	No
`domain`	No
`status`	Yes
`balance`	No
`message`	No
`success`	Yes
`order_id`	No
`funds_added`	No
`payment_code`	Yes
`stop_polling`	No	Only with status 'pending': true means stop polling and show user_message.
`user_message`	No	Highlighted markdown warning to show the user verbatim when stop_polling is true.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

addedOutput schema / properties / url / description

Added value: +"Where the user can see the result: My Domains (/dashboard/registrar) for a registration or marketplace purchase, the Atom dashboard (/dashboard) for add funds."

changedOutput schema / required

Previous value: -[
-  "success",
-  "status",
-  "payment_code",
-  "url"
-]New value: +[
+  "success",
+  "status",
+  "payment_code"
+]

Changed3 schema fields changedOct 2, 2026

addedInput schema / properties / wait_seconds

Added value: +{
+  "default": 10,
+  "description": "How long the server may wait for the payment before answering (default 10). Use 0 for an instant check.",
+  "maximum": 15,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / stop_polling

Added value: +{
+  "description": "Only with status 'pending': true means stop polling and show user_message.",
+  "type": "boolean"
+}

addedOutput schema / properties / user_message

Added value: +{
+  "description": "Highlighted markdown warning to show the user verbatim when stop_polling is true.",
+  "type": "string"
+}

AddedSep 30, 2026

TDQS

A4.4/5.0

Behavior3/5

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

Discloses genuinely useful behavior not in the annotations: a ~10s server-side wait with re-check, safety of back-to-back calls, the ~15 minute stop_polling cutoff, and the semantics of all four terminal statuses. However, the claim that a call 'complete[s] the purchase / registration / funds credit' describes a state mutation, which conflicts with readOnlyHint=true (and the pure-read implication of destructiveHint=false) — a safety-relevant conflict that caps the score despite otherwise excellent disclosure.

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 side effect, then a clearly labeled POLLING block and an enumerated status list — a structure an agent can parse under time pressure. Slight redundancy between 'safe to call back-to-back' and 'no need to wait between calls', and the status enumeration is dense, but nearly every sentence carries operational content.

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 two-parameter polling tool with an output schema and full schema coverage, the description supplies the missing operational layer: the polling loop, the stop condition, the timing model, and the per-status follow-up action. Nothing an agent needs in order to call it correctly and react to results is absent.

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, and the description goes beyond it by explaining why no client-side delay is needed ('each call waits up to ~10 seconds server-side and re-checks'), which gives meaning to wait_seconds and to back-to-back invocation. It does not restate the payment_code provenance beyond naming the producing tools, which is adequate.

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 Coinbase (USDC) payment') and names the exact sibling tools that produce the payment_code it consumes, so the agent can place it in the pay-flow without opening any schema. It also states what the call achieves ('complete the purchase / registration / funds credit'), which no sibling name conveys.

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 polling protocol: keep calling while status is 'pending' and stop_polling is false, no delay needed, stop when stop_polling is true and surface user_message verbatim, and re-call later if the user claims payment. Each terminal status ('failed' → offer a new link, 'refunded', 'needs_support') is paired with the action to take, which is exactly the when-to-use/how-to-react guidance an agent 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.