Skip to main content
Glama
Sign In
Cloady

Cloady

Official
by Cloady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Register Domain

registerDomain
Destructive

Registers a domain for its minimum term and charges the workspace card; dry-run quotes the price and checks availability, while WHOIS privacy, auto-renew, and Cloady DNS are configured by default.

Instructions

Registers a domain for its registry's minimum term, usually a year, charged to the workspace's card: the owner's account card, or the workspace's own when one is pinned. The registrant becomes the domain's legal owner, and the registry may email them to confirm the address. WHOIS privacy and auto-renew are on unless set to false. Without nameservers, Cloady points the domain and every subdomain at Cloady, so attaching any of them to an application with createDomain needs no DNS change. dryRun quotes the price and checks the name can be registered here without charging; premium names, orders over $100 and extensions whose registry needs more than a contact can't be. A card the bank wants to authenticate answers 402 payment_action_required with clientSecret, paymentIntentId and publishableKey in details: confirm it with Stripe.js, then repeat the request with paymentIntentId. If registration fails after the charge, the charge is refunded. Needs the developer role.

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": {
      "workspaceSlug": "<workspaceSlug>"
    },
    "name": "registerDomain"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestBodyNoThe JSON request body.
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only flag destructive/openWorld/not-readOnly; the description goes far beyond by disclosing what is charged and to which card, that the registrant becomes legal owner and may receive a registry email, that privacy and auto-renew default to on, and that failed registrations are refunded. The 402 payment_action_required flow with `clientSecret`/`paymentIntentId`/`publishableKey` is fully spelled out. Only the success response shape is left implicit.

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?

One dense paragraph, front-loaded with purpose then defaults, then DNS behavior, then the dryRun and payment edge cases — a sensible priority order. Some sentences pack multiple clauses (card selection, refund, role), but none are filler.

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

Completeness4/5

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

For a money-moving, destructive, open-world tool with no output schema, the description covers cost, defaults, ownership, DNS side effects, error/payment-recovery path, refund guarantee, and authorization. The remaining gap is what a successful registration returns (e.g., identifiers or expiry) for chaining into createDomain.

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?

With schema coverage at 50%, the description compensates well: it explains that `registrant` defines legal ownership and is emailed, that omitting `nameservers` triggers Cloady DNS for the domain and all subdomains, that `dryRun` skips both charge and registration, and that `paymentIntentId` replays an authenticated 402 payment. Only `workspaceSlug` and a few nested registrant fields are left to the schema.

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?

Opens with a precise verb+resource ("Registers a domain") plus the commercial term (registry minimum term, charged to the workspace's card). It also distinguishes itself from the sibling createDomain by explaining that Cloady's default nameservers mean attaching the domain later "needs no DNS change", so an agent can tell purchasing apart from attaching.

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?

Explicitly routes callers: use `dryRun` to quote and validate without charging, use `createDomain` to attach the domain to an application, and omit `nameservers` to get Cloady DNS. It also declares hard exclusions (premium names, orders over $100, extensions needing more than one contact) and the developer-role prerequisite.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools