Skip to main content
Glama

Create a domain order

create_order
DestructiveIdempotent

Create a registration order (a price-locked quote). A 402 is the payment challenge, not an error: pay the existing invoice and poll poll_url / check_order — do not create_order again for the same domain while status is awaiting_payment (repeats return the same order with reused:true). Returns quote{price_usd, locked_until}, pay{x402, transfer, checkout_url, poll_url}, payment requirements (exact amount_units — do not round to price_usd) and checkout_url. Policy: check availability right before buying, show the quote to the human and get confirmation before paying; pass idempotency_key (retries with the same key never create a second order; if omitted, identical calls within 15 min share a key, and any open unpaid register for the same buyer+domain is reused). pay_with=balance pays instantly from prepaid balance. Gasless: retry with x402 PAYMENT-SIGNATURE on this order pay URL, or POST /api/v1/register. Card: the 402 also carries stripe_link and stripe_card; hand the human checkout_url. dry_run=true previews quote, renewal and blockers without creating an order.

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

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)
yearsNo
domainYes
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.
dry_runNopreview only, nothing created or charged
pay_withNo
showcaseNoOpt in to the public /showcase listing (only if the user asked)
nameserversNo
showcase_titleNo
idempotency_keyNo
showcase_categoryNoRequired when showcase is true
showcase_descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ref / description
      Previous value: -"referrer code"New 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. Changed1 schema field changed
    • addedInput schema / properties / dry_run
      Added value: +{
      +  "description": "preview only, nothing created or charged",
      +  "type": "boolean"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / showcase_category
      Added value: +{
      +  "description": "Required when showcase is true",
      +  "enum": [
      +    "ai-agents",
      +    "crypto-web3",
      +    "saas-tools",
      +    "shops",
      +    "blogs-media",
      +    "portfolios",
      +    "other"
      +  ],
      +  "type": "string"
      +}
  5. Changed3 schema fields changed
    • removedInput schema / properties / pay_with / description
      Removed value: -"crypto (default: USDC/USDT, x402 or transfer), balance (prepaid balance), or card: returns a single-use Stripe pay link that a person opens and pays; the agent does not pay by card itself"
    • changedInput schema / properties / pay_with / enum
      Previous value: -[
      -  "crypto",
      -  "balance",
      -  "card"
      -]New value: +[
      +  "crypto",
      +  "balance"
      +]
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "body": {
      -      "type": [
      -        "object",
      -        "array",
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "card": {
      -      "properties": {
      -        "card_fee_usd": {
      -          "type": "string"
      -        },
      -        "card_pay_url": {
      -          "type": "string"
      -        },
      -        "code": {
      -          "enum": [
      -            "SCA_REQUIRED"
      -          ],
      -          "type": "string"
      -        },
      -        "message": {
      -          "type": "string"
      -        },
      -        "order_id": {
      -          "type": "string"
      -        },
      -        "price_usd": {
      -          "type": "string"
      -        },
      -        "status": {
      -          "enum": [
      -            "needs_human"
      -          ],
      -          "type": "string"
      -        },
      -        "total_usd": {
      -          "type": "string"
      -        }
      -      },
      -      "type": "object"
      -    },
      -    "http_status": {
      -      "type": "integer"
      -    },
      -    "order": {
      -      "properties": {
      -        "checkout_url": {
      -          "type": "string"
      -        },
      -        "domain": {
      -          "type": "string"
      -        },
      -        "id": {
      -          "type": "string"
      -        },
      -        "kind": {
      -          "type": "string"
      -        },
      -        "price_usd": {
      -          "type": "string"
      -        },
      -        "status": {
      -          "type": "string"
      -        },
      -        "years": {
      -          "type": "integer"
      -        }
      -      },
      -      "type": "object"
      -    }
      -  },
      -  "required": [
      -    "http_status",
      -    "body"
      -  ],
      -  "type": "object"
      -}New value: +null
  6. Changed3 schema fields changed
    • addedInput schema / properties / pay_with / description
      Added value: +"crypto (default: USDC/USDT, x402 or transfer), balance (prepaid balance), or card: returns a single-use Stripe pay link that a person opens and pays; the agent does not pay by card itself"
    • changedInput schema / properties / pay_with / enum
      Previous value: -[
      -  "crypto",
      -  "balance"
      -]New value: +[
      +  "crypto",
      +  "balance",
      +  "card"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "body": {
      +      "type": [
      +        "object",
      +        "array",
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "card": {
      +      "properties": {
      +        "card_fee_usd": {
      +          "type": "string"
      +        },
      +        "card_pay_url": {
      +          "type": "string"
      +        },
      +        "code": {
      +          "enum": [
      +            "SCA_REQUIRED"
      +          ],
      +          "type": "string"
      +        },
      +        "message": {
      +          "type": "string"
      +        },
      +        "order_id": {
      +          "type": "string"
      +        },
      +        "price_usd": {
      +          "type": "string"
      +        },
      +        "status": {
      +          "enum": [
      +            "needs_human"
      +          ],
      +          "type": "string"
      +        },
      +        "total_usd": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "http_status": {
      +      "type": "integer"
      +    },
      +    "order": {
      +      "properties": {
      +        "checkout_url": {
      +          "type": "string"
      +        },
      +        "domain": {
      +          "type": "string"
      +        },
      +        "id": {
      +          "type": "string"
      +        },
      +        "kind": {
      +          "type": "string"
      +        },
      +        "price_usd": {
      +          "type": "string"
      +        },
      +        "status": {
      +          "type": "string"
      +        },
      +        "years": {
      +          "type": "integer"
      +        }
      +      },
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "http_status",
      +    "body"
      +  ],
      +  "type": "object"
      +}
  7. Changed3 schema fields changed
    • addedInput schema / properties / showcase
      Added value: +{
      +  "description": "Opt in to the public /showcase listing (only if the user asked)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / showcase_description
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / showcase_title
      Added value: +{
      +  "type": "string"
      +}
  8. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say it mutates and is idempotent; the description adds far more: 402 is a payment challenge rather than an error, repeats return the same order with reused:true, amount_units must not be rounded to price_usd, and the gasless/card payment paths. Idempotency semantics (same-key retries never duplicate; omitted key shares a key across identical calls within 15 min and reuses any open unpaid order) go well beyond the idempotentHint flag.

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 the critical 402/idempotency rule, and nearly every clause carries operational information. It is dense and runs several flows (crypto, gasless, card, balance, dry_run) into one block, which costs some readability but not much in wasted words.

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 destructive, payment-bearing tool with 14 parameters and no output schema, the description supplies the missing return-value information (quote{price_usd, locked_until}, pay{x402, transfer, checkout_url, poll_url}, stripe_link/stripe_card) and the recovery path after a 402. An agent has what it needs to call and interpret it correctly.

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 only 50%, but the description compensates for the highest-risk parameters: idempotency_key behavior, pay_with=balance semantics, dry_run meaning, and the quote/pay return objects. Several parameters (years, nameservers, showcase_title, showcase_description) remain unexplained in both places, which keeps this below a 5.

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?

"Create a registration order (a price-locked quote)" gives a specific verb, resource, and the semantic nature of the result (a quote, not a purchase). The parenthetical immediately tells an agent this call does not itself complete payment, which separates it from pay_order and quote_domain.

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?

Explicit when-not guidance: do not re-call create_order while status is awaiting_payment, instead pay and poll poll_url / check_order. It also names the correct workflow (check availability right before buying, show quote and get human confirmation before paying) and when to prefer dry_run=true for previews.

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