Skip to main content
Glama

Transfer a domain in

transfer_domain
Destructive

Transfer a domain in from another registrar using its auth/EPP code; paid in USDC (adds 1 year). Unlock it at the current registrar first. Completes in ~5-7 days.

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>",
      "auth_code": "<auth_code>"
    },
    "name": "transfer_domain"
  }
}

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.
pay_withNo
auth_codeYes
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. 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
  4. 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"
      +}
  5. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The description adds real value beyond the annotations: a 5-7 day completion window, the one-year renewal effect, the unlock prerequisite, and the payment currency. However, 'paid in USDC' sits awkwardly against a schema that exposes USDT and a 'balance' option, and it says nothing about what happens if the transfer fails or how funds are handled for a destructive, non-idempotent, money-spending 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?

Compact and largely front-loaded, but the sentence is packed into a semicolon chain and buries the operationally critical unlock prerequisite mid-string after the payment detail. It is efficient without being optimally ordered.

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, open-world, non-idempotent tool with no output schema, the essential call-shaping facts (auth code, unlock first, duration, cost model) are present. Failure/refund behavior and how the multi-chain, multi-token, balance-vs-crypto payment parameters interact are left unaddressed.

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?

With only 44% schema coverage across 9 parameters, the description picks up some of the slack: it explains auth_code as an EPP code, and clarifies years via 'adds 1 year' and the payment currency. It says nothing about idempotency_key, ref, chain, pay_with, or api_key, so several parameters remain explainable only from the schema.

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?

States a specific verb and resource ('Transfer a domain in from another registrar') and adds scope detail: auth/EPP code required, paid in USDC, adds one year. It is clearly distinguishable from renew_domain or buy-style siblings in intent, though it never names an alternative explicitly.

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?

Provides one concrete prerequisite ('Unlock it at the current registrar first') and an implied context (the domain currently lives at another registrar), but gives no explicit when-not guidance or pointer to a sibling for related actions like renew_domain or quote_domain.

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