Prepare a transfer
transfer_namePrepare transferring an ENS name to another address for the user to sign in their own wallet, e.g. 'Send alice.eth to bob.eth'. Nothing is sent. The recipient gets full control; double-check the address. For unwrapped ENSv1 .eth names, role: registrant moves only the registration and keeps the manager.
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": {
"name": "<name>",
"account": "<account>",
"to": "<to>"
},
"name": "transfer_name"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Recipient: an address or an ENS name | |
| name | Yes | ENS name as the user wrote it, e.g. nick.eth; normalised by the server (ENSIP-15) | |
| role | No | owner (default): everything; registrant: only the .eth registration (ENSv1) | |
| account | Yes | Account that will sign the transactions: an address (0x…) or an ENS name | |
| records | No | ENSv2: keep (default) the sender's access to the name's records, or hand it over |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cost | Yes | ||
| plan | Yes | Handle of this plan for get_plan; pass it back unchanged | |
| calls | Yes | Unsigned calls, in order, for the account's wallet | |
| chain | Yes | ||
| steps | Yes | ||
| issues | Yes | Why a checked step would fail | |
| account | Yes | ||
| deploys | No | Contracts the plan deploys, at addresses known in advance | |
| signing | Yes | How to sign the steps, in plain words | |
| summary | Yes | ||
| warnings | Yes | ||
| willSucceed | Yes | Whether the steps that can be checked now would succeed if signed now | |
| requirements | Yes | What the account needs before signing, e.g. a token balance |