Skip to main content
Glama

Create a multi-domain cart

create_cart
Destructive

Register up to 20 available domains with ONE payment (exact total in the 402). Returns a price-locked quote, checkout_url for a human to pay, and is idempotent via idempotency_key. After payment each is registered; any failure is refunded to prepaid balance.

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": {
      "domains": "<domains>"
    },
    "name": "create_cart"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoAffiliate ref code. Earn $0.60 per .com you refer, $0.51 per .xyz, paid weekly in USDC.
chainNopayment network (default base). hyperevm = HyperEVM (chain 999, USDC/USDT0), bsc = BNB Chain (56, 18-decimal USDC/USDT)
tokenNostablecoin (default USDC)
api_keyNoOptional. Guest or dashboard API key (sd_live_…). Prefer Authorization: Bearer <key> on the MCP connection; if your client cannot set headers, pass the key here.
domainsYes
nameserversNo
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / ref / description
      Added value: +"Affiliate ref code. Earn $0.60 per .com you refer, $0.51 per .xyz, paid weekly in USDC."
  2. Changed1 schema field changed
    • addedInput schema / properties / api_key
      Added value: +{
      +  "description": "Optional. Guest or dashboard API key (sd_live_…). Prefer Authorization: Bearer <key> on the MCP connection; if your client cannot set headers, pass the key here.",
      +  "type": "string"
      +}
  3. First observed

TDQS

B3/5.0
Behavior1/5

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

The description adds useful behavior such as the return of a price-locked quote, checkout_url, and refunds to prepaid balance. However, it says the operation 'is idempotent via idempotency_key' while the annotations declare idempotentHint=false, which is a direct contradiction about a critical retry-safety property.

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?

The description is three dense sentences with the core action and payment model front-loaded. Almost every phrase carries useful information, though the parenthetical about the 402 total is slightly cryptic without more context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, multi-parameter payment tool with no output schema, the description covers the key return values and post-payment refund behavior. It still leaves gaps around quote expiry, checkout URL lifetime, nameserver handling, and the exact conditions under which the operation is or is not idempotent.

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 description coverage is 57%, with ref, chain, token, and api_key already documented in the schema. The description adds meaning for the otherwise undocumented idempotency_key and the domains array by specifying the maximum of 20, but it does not explain nameservers or payment behavior beyond the single-payment model.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: register up to 20 available domains with one payment. It clearly explains that this creates a price-locked quote and checkout_url rather than completing a purchase, but it does not explicitly differentiate itself from siblings such as quote_domain or buy_with_balance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: this is for batch domain registration paid through a single human checkout. However, the description does not state when to use this instead of quote_domain, create_order, or buy_with_balance, nor does it give explicit exclusions or prerequisites.

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.

Resources