TON NFT Operations
View and transfer NFTs on the TON blockchain.
MCP Tools
| Tool | Required | Optional |
|---|---|---|
get_nfts |
— | limit, offset, walletSelector |
get_nfts_by_address |
address |
limit, offset |
get_nft |
nftAddress |
— |
build_nft_transfer |
nftAddress, toAddress |
comment, walletSelector |
emulate_transaction |
messages |
validUntil |
send_raw_transaction |
messages |
validUntil, fromAddress, walletSelector |
build_nft_transfer does NOT broadcast — it returns ready-to-send transaction.messages plus transaction.fromAddress. Preview with emulate_transaction, then broadcast with send_raw_transaction.
Workflows
List My NFTs
- Call
get_nftsto list NFTs in the active wallet - Use
limitandoffsetfor pagination
View NFT Details
- Call
get_nftwith thenftAddress
Send an NFT
- Call
get_nftsto find the NFT address if the user doesn't have it - Call
build_nft_transferwithnftAddressandtoAddressto build the transaction (it is NOT sent) - Preview it with
emulate_transactionusing the returnedtransaction.messages(recommended before broadcasting) - Ask one short yes/no confirmation before transferring the NFT
- Broadcast with
send_raw_transactionpassing thetransaction.messagesandtransaction.fromAddress(the NFT transfer is bound to the wallet it was built for) - Poll
get_transaction_statuswith the returnednormalizedHashuntil status iscompletedorfailed(seeton-balanceskill)
Notes
build_nft_transferbuilds the transaction only;send_raw_transactionis the tool that signs and broadcasts it- Use
emulate_transactionto preview expected balance changes before broadcasting (fake signature) - Always confirm with the user before transferring an NFT; prefer the host client's structured confirmation UI when available, otherwise accept natural-language yes/no and do not require a fixed confirmation phrase
- If no wallet is configured, use the
ton-create-walletskill first