Skip to main content
Glama

Prepare domain transfers

prepare_domain_transfers

Prepares moving one or more domains the customer already owns at ANOTHER registrar to Squish, and returns ONE checkout link for all of them: each eligible domain is priced and placed in a single cart on their account; the link opens the normal checkout. No money moves when this tool runs and no auth codes are needed here: after paying, the customer enters each transfer (EPP/auth) code from the Domains card in their dashboard, so NEVER ask for a code in the conversation. A .uk domain (.co.uk, .org.uk, .uk …) has NO code at all: the current registrar changes its IPS tag to NAMESILO and the customer confirms that from the same Domains card. conversation and never pass one to this tool. Two-step: (1) confirm:false previews, PER DOMAIN, whether it can move (and if not, why: already at Squish, not registered anywhere — use prepare_domain_purchase —, locked, too recently registered, restricted or premium ending) and the transfer price, plus the total and the three things they do at the current registrar; relay the ineligible list and ask for an explicit yes. (2) ONLY after an explicit yes in their most recent message, call with confirm:true for the link; the cart holds the eligible domains only. Up to 50 domains per call; split a longer list. Use get_my_domain_transfers afterwards to report where each transfer stands.

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

Input Schema

NameRequiredDescriptionDefault
confirmNofalse (default) returns the per-domain preview; true creates the cart and the checkout link. Pass true ONLY after explicit user confirmation.
domainsYesThe exact domains to transfer in, e.g. ["example.com", "example.net"]. One to fifty.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond annotations, it discloses that no money moves and no auth codes are needed at this stage, that the customer later enters EPP codes from the dashboard, and that .uk domains use an IPS tag change instead. It also clarifies cart contents and the 50-domain limit, which are material for a non-read-only, non-destructive operation.

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

Conciseness3/5

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

The description is front-loaded and dense, but it repeats auth-code warnings and contains a stray fragment ('conversation and never pass one to this tool'), which weakens structure. It is appropriately detailed for a complex two-step tool but not maximally concise.

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 two-step domain-transfer preparation tool with no output schema, it covers eligibility outcomes, pricing preview, cart/link behavior, special .uk handling, limits, and the follow-up tool. Nothing essential for correct invocation appears 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?

The schema already documents both parameters at 100% coverage. The description adds workflow meaning for confirm (preview vs. cart creation, explicit-yes gate) and notes the 50-domain cap and splitting behavior, though it doesn't add input syntax beyond 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?

The description gives a specific verb and resource—moving domains the customer owns at another registrar to Squish—and states that it returns a single checkout link. It explicitly contrasts with prepare_domain_purchase for unregistered domains, so the agent can distinguish it from that sibling tool.

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?

It spells out the two-step flow: confirm:false previews per-domain eligibility and pricing, and confirm:true is allowed only after an explicit yes in the most recent message. It also names get_my_domain_transfers for follow-up and prepare_domain_purchase for a different case.

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