Atom.com — Premium Domains

Get add funds Coinbase (USDC) pay link

get_add_funds_coinbase_pay_link

Read-only

Get a Coinbase checkout link, paid in USDC, that adds funds to the user's Atom account balance (the balance register_domain and purchase_domain pay from). Returns two URLs for the same payment: x402_url — an agent with an x402-capable crypto wallet (e.g. a Coinbase agentic wallet) pays it directly (POST, 402 Payment Required, signed retry); and checkout_url — the hosted page a human opens in a browser to pay with their own wallet. Use this when a balance purchase reports insufficient funds and the user wants to top up with crypto/USDC.

Always present the exact server-computed price returned here — never recompute it. This tool charges nothing by itself.

RIGHT AFTER handing over the link (or paying x402_url), start polling get_coinbase_payment_status with the returned payment_code — keep calling it while status is 'pending' and stop_polling is false (each call waits ~10s server-side). If stop_polling turns true, stop and show its user_message exactly as given; check again when the user says they have paid. The funds are only credited once that reports status 'completed' (poll again while it reports 'pending'). Then retry the balance purchase.

Input Schema

Name	Required	Description	Default
`amount`	Yes	USD amount to add to the Atom account balance.

Output Schema

Name	Required	Description
`url`	Yes
`price`	No	Exact total the checkout charges.
`success`	Yes
`currency`	No
`x402_url`	No	x402 payment endpoint for agent wallets: POST it, get 402 Payment Required, sign and retry. Prefer this over checkout_url when an x402 wallet is connected.
`checkout_url`	Yes	Hosted Coinbase checkout page — give this to a human to pay in a browser.
`funds_amount`	No	Amount that will be credited to the balance.
`payment_code`	Yes	Pass to get_coinbase_payment_status after paying.
`processing_fee`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026

changedOutput schema / properties / checkout_url / description

Previous value: -"Coinbase checkout URL (x402-payable). Hand to an x402 wallet or the user."New value: +"Hosted Coinbase checkout page — give this to a human to pay in a browser."

addedOutput schema / properties / x402_url

Added value: +{
+  "description": "x402 payment endpoint for agent wallets: POST it, get 402 Payment Required, sign and retry. Prefer this over checkout_url when an x402 wallet is connected.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

AddedSep 30, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations: explains that the tool charges nothing by itself (consistent with readOnlyHint), that payment happens out-of-band via a 402 challenge and signed retry, that each status poll waits ~10s server-side, and that funds are credited only once status reports 'completed'. The 'never recompute the price' rule is a non-obvious behavioral constraint that would otherwise cause errors.

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 core purpose and return shape, then the usage trigger, then the follow-up workflow — a sensible ordering. It is on the long side and carries polling mechanics that arguably belong to get_coinbase_payment_status, but every sentence provides actionable constraint rather than filler.

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 an output schema existing, the description still describes the two returned URLs at the level an agent needs to act on them, and it covers the full lifecycle from link generation through credit confirmation. Nothing needed to call it correctly and safely 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 'amount' parameter, so baseline would be 3; the description adds that the price is server-computed and must be presented verbatim rather than derived, which meaningfully constrains how the amount is used. It does not, however, clarify whether 'amount' is the user-supplied target or the server-returned price, leaving slight ambiguity.

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 a Coinbase checkout link, paid in USDC, that adds funds to the user's Atom account balance') and disambiguates scope from sibling pay-link tools by naming the balance used by register_domain and purchase_domain. It also enumerates the two returned URLs and what each is for, so an agent can pick it apart from get_domain_purchase_coinbase_pay_link without opening either 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 ('Use this when a balance purchase reports insufficient funds and the user wants to top up with crypto/USDC'), the immediate follow-up step (poll get_coinbase_payment_status with the returned payment_code), the stopping condition (stop_polling true / status 'completed'), and the final action (retry the balance purchase). Alternatives are named by tool, not just implied.

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.