Skip to main content
Glama

Atom.com — Premium Domains

by com.atom

buy_ai_tokens

Destructive

Purchase AI Tokens ($0.10 per token) by charging a Stripe Shared Payment Token (SPT) — for users with no Atom balance. This SPENDS REAL MONEY and requires the 'domains:register' scope.

MANDATORY three-step flow — never skip a step:

  1. Call with confirm=false to get a QUOTE: price is entirely server-authoritative ($0.10 x token_count) — never assume or pass a price.

  2. Call again with confirm=true, the SAME idempotency_key, and NO payment_token: returns a structured payment_required challenge (amount, currency).

  3. Once a Shared Payment Token is obtained for that exact amount, call a third time with confirm=true, the SAME idempotency_key, and payment_token set. Payment is captured FIRST; tokens are only credited after that succeeds.

PAYMENT PRIORITY for AI Tokens: this tool is priority 1 — try it first, using whatever payment method your own platform can already supply for the payment_token. Only if you have no way to obtain a payment_token here, fall back to priority 2: get_ai_tokens_pay_link, paid via link-cli's tools (e.g. mpp_pay), if those are present in this session. There is no checkout-link fallback for AI Tokens.

Rules: never assume or pass a price. Reuse one idempotency_key across all calls for the same intent. If crediting fails AFTER payment succeeds, no refund is issued automatically — the result says so explicitly; do not tell the user a refund is coming.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNofalse returns a quote; true attempts payment + crediting.
token_countYesNumber of AI Tokens to purchase (1-100000).
payment_tokenNoShared Payment Token authorizing the exact quoted amount. Omit to receive the payment_required challenge.
idempotency_keyYesClient-generated unique key; identical across all calls for the same intended purchase.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
priceNo
stageYes
balanceNoAI Token balance after crediting (credited stage).
successYes
currencyNo
challengeNoPresent when stage=payment_required.
token_countYes
idempotency_keyNo
payment_intent_idNo

TDQS

A5/5.0
Behavior5/5

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

Beyond the destructiveHint and openWorldHint annotations, the description discloses critical behavioral traits: 'SPENDS REAL MONEY', requires the 'domains:register' scope, payment is captured before crediting, and if crediting fails after payment, no automatic refund is issued. This adds significant context and no contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but every sentence earns its place, given the complex payment flow. It is well-structured with numbered steps and clear rules, front-loading the purpose and the most critical warning about real money. No fluff or redundant repetition of schema details.

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?

The tool has a complex multi-step payment process, and the description covers all essential aspects: the three-step flow, fallback options, no-refund policy, and the exact behavior of payment capture. The output schema exists but the description still clarifies what to expect at each step, making it complete for an agent to use confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

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

Although schema coverage is 100%, the description adds crucial meaning: pricing is server-authoritative and must not be assumed or passed, the same idempotency_key must be reused across all calls, and payment_token is omitted to receive a challenge. These details go far beyond the bare parameter descriptions and are essential for correct invocation.

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?

The description opens with a specific verb and resource: 'Purchase AI Tokens ($0.10 per token) by charging a Stripe Shared Payment Token (SPT)' and clearly scopes it to 'users with no Atom balance'. It distinguishes itself from sibling tools by explicitly setting priority over get_ai_tokens_pay_link. The purpose is unambiguous and not a mere restatement of the name.

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?

The description provides extensive when-to-use guidance: it says to try this tool first (priority 1) and specifies exactly when to fall back to get_ai_tokens_pay_link. It also gives a mandatory three-step flow with confirmation flags and idempotency key reuse, leaving no ambiguity about the correct procedure versus alternatives.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation2/5

Several tools serve the same resource+action through different payment channels (e.g., register_domain, register_domain_spt, get_domain_register_pay_link; purchase_domain, get_domain_purchase_pay_link, get_checkout_link; buy_ai_tokens, get_ai_tokens_pay_link). brainstorm_names is explicitly a duplicate of search_brandable_domains, so the set has multiple confusing overlaps despite detailed descriptions.

Naming Consistency4/5

Most tool names follow a predictable snake_case verb_noun pattern (appraise_domain, check_domain_availability, purchase_domain, screen_trademark_conflicts). Minor deviations like brainstorm_names, register_domain_spt, and get_checkout_link break the pattern slightly but remain readable and recognizable.

Tool Count3/5

Sixteen tools is right at the boundary where a tool set starts to feel heavy. Many tools are legitimately needed for discovery, purchasing, and payment routing, but the duplicate name-generation tool and the multiple payment-route variants add unnecessary bulk.

Completeness4/5

The core domain lifecycle is well covered: search/discovery, availability checks, details, appraisal, trademark screening, registrant contact, and both fresh registration and marketplace purchase paths are present. Minor gaps exist around post-purchase management, account balance visibility, and offer submission, but the main user journey has no significant dead ends.

Resources