Skip to main content
Glama

registerDomain

registerDomain: Stage registration of a new domain name. Deducts from account balance. The DNS zone is initialised automatically after registration (asynchronously; if createDnsRecord right after registration reports a missing zone, retry after a few seconds). Pass initializeDnsZone:false to opt out. Returns an actionId: present the summary to the user, then call executeConfirmedAction with the actionId if they approve. Owner: pass registrantId (a saved contact from createContact/listContacts) or an inline registrantInfo. For .al domains: first createContact with registryAttributes (see its schema), then pass the returned id as registrantId; ask the user for nameservers rather than guessing. A .al domain ends in pendingCreate until the registry (AKEP) approves it by hand - that is success, not a failure.

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>",
      "years": "<years>",
      "nameservers": "<nameservers>"
    },
    "name": "registerDomain"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsYesRegistration period in years, 1-10.
domainYesFully qualified domain name to register, like "example.com", without scheme.
autoRenewNoEnable automatic renewal; defaults to true.
sessionKeyNoSession key (osk_...) returned by checkDeviceLoginStatus. Pass it on every call when logged in via the in-chat device flow; omit when connected via OAuth.
nameserversYesList of nameserver hostnames, e.g. ["ns1.example.com", "ns2.example.com"].
registrantIdNoid of a saved contact (createContact/listContacts) to use as registrant, and as admin/tech/billing contact. REQUIRED for .al: without it the account's default contact becomes the registrant.
registrantInfoNoInline registrant contact of the domain owner: firstName, lastName, email, phone (+CC.number), and address (street, city, postalCode, country as 2-letter ISO code). Omit when passing registrantId. Not usable for .al.
initializeDnsZoneNoInitialise the DNS zone after registration; defaults to true.
privacyProtectionNoEnable WHOIS privacy protection; defaults to true.
registryAttributesNoOptional per-order override of the registrant's registry fields (same shape as createContact.registryAttributes). Only for .al.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / registrantId
      Added value: +{
      +  "description": "id of a saved contact (createContact/listContacts) to use as registrant, and as admin/tech/billing contact. REQUIRED for .al: without it the account's default contact becomes the registrant.",
      +  "type": "integer"
      +}
    • changedInput schema / properties / registrantInfo / description
      Previous value: -"ICANN registrant contact of the domain owner: firstName, lastName, email, phone (+CC.number), and address (street, city, postalCode, country as 2-letter ISO code)."New value: +"Inline registrant contact of the domain owner: firstName, lastName, email, phone (+CC.number), and address (street, city, postalCode, country as 2-letter ISO code). Omit when passing registrantId. Not usable for .al."
    • addedInput schema / properties / registryAttributes
      Added value: +{
      +  "description": "Optional per-order override of the registrant's registry fields (same shape as createContact.registryAttributes). Only for .al.",
      +  "properties": {
      +    "docnr": {
      +      "type": "string"
      +    },
      +    "doctype": {
      +      "type": "string"
      +    },
      +    "entityType": {
      +      "type": "string"
      +    },
      +    "nipt": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "domain",
      -  "years",
      -  "registrantInfo",
      -  "nameservers"
      -]New value: +[
      +  "domain",
      +  "years",
      +  "nameservers"
      +]
  2. Changed7 schema fields changed
    • addedInput schema / properties / autoRenew / description
      Added value: +"Enable automatic renewal; defaults to true."
    • addedInput schema / properties / domain / description
      Added value: +"Fully qualified domain name to register, like \"example.com\", without scheme."
    • addedInput schema / properties / initializeDnsZone / description
      Added value: +"Initialise the DNS zone after registration; defaults to true."
    • addedInput schema / properties / nameservers / description
      Added value: +"List of nameserver hostnames, e.g. [\"ns1.example.com\", \"ns2.example.com\"]."
    • addedInput schema / properties / privacyProtection / description
      Added value: +"Enable WHOIS privacy protection; defaults to true."
    • addedInput schema / properties / registrantInfo / description
      Added value: +"ICANN registrant contact of the domain owner: firstName, lastName, email, phone (+CC.number), and address (street, city, postalCode, country as 2-letter ISO code)."
    • addedInput schema / properties / years / description
      Added value: +"Registration period in years, 1-10."
  3. First observed

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 by disclosing cost impact ('Deducts from account balance'), asynchronous DNS zone initialisation with a concrete retry pattern for createDnsRecord, and the .al pendingCreate manual-approval state being success rather than failure. That is exactly the non-obvious behavior an agent would otherwise misread as an error.

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 dense with value, but delivered as one long run-on paragraph mixing workflow, cost, DNS timing, ownership, and .al edge cases. Bullet separation or short labeled clauses would make the .al-specific guidance easier to scan.

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 10-parameter, multi-step, confirmation-gated mutation with no output schema, the description covers the whole flow: staging, the returned actionId and its follow-up, contact prerequisites, async DNS timing, and registry-specific states. Nothing an agent needs to call it correctly 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%, so the baseline is 3; the description adds real meaning on top — registrantId must come from createContact/listContacts and is effectively required for .al, registrantInfo is not usable for .al, and initializeDnsZone:false is the opt-out. It does not explain years/autoRenew/privacyProtection beyond the schema, but those are already well documented.

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 specific verb+resource: 'Stage registration of a new domain name', and immediately clarifies the two-phase nature (stage now, then executeConfirmedAction). An agent can distinguish this from renewDomain, transferDomain, or lockDomain without opening any 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?

Explicit routing: present actionId to the user, then call executeConfirmedAction on approval; pass registrantId from createContact/listContacts or use inline registrantInfo; for .al, first createContact with registryAttributes then pass the id. Also states when to retry and when to opt out via initializeDnsZone:false.

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.