How do I install the Ton Send skill?

Run npx skillmds@latest add ton-org/ton-send in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ton Send safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ton Send?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ton Send free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ton Send?

ton-org (@ton-org) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ton Send by ton-org — Agent Skill

Name: Ton Send
Author: ton-org

Ton Send

Send GRAM (ex. TON) or jettons (tokens) to an address or TON DNS domain. Use when the user wants to send GRAM (ex. TON), transfer tokens, send jettons, pay someone, send funds to a .ton or .t.me domain, or transfer assets on the TON blockchain.

ton-org 4ad2a9d 3.2 KB Updated Sep 17, 2026

File contents

Send GRAM (ex. TON) & Tokens

Transfer GRAM (ex. TON) or jettons to any address. Supports TON DNS resolution for .ton and .t.me domains.

MCP Tools

Tool	Required	Optional
`build_ton_transfer`	`toAddress`, `amount`	`comment`, `walletSelector`
`build_jetton_transfer`	`toAddress`, `jettonAddress`, `amount`	`comment`, `walletSelector`
`emulate_transaction`	`messages`	`validUntil`
`send_raw_transaction`	`messages`	`validUntil`, `fromAddress`, `walletSelector`
`resolve_dns`	`domain`	—
`back_resolve_dns`	`address`	—

build_ton_transfer and build_jetton_transfer do NOT broadcast — they return ready-to-send transaction.messages plus transaction.fromAddress. Preview with emulate_transaction, then broadcast with send_raw_transaction.

Workflows

Send GRAM (ex. TON)

If the user provides a DNS name (e.g., foundation.ton, user.t.me) instead of a raw address, call resolve_dns first
Call build_ton_transfer with address and amount to build the transaction (it is NOT sent)
Preview it with emulate_transaction using the returned transaction.messages (recommended before broadcasting)
Ask one short yes/no confirmation that restates the amount and recipient
Broadcast with send_raw_transaction passing the transaction.messages and transaction.fromAddress
Poll get_transaction_status with the returned normalizedHash until status is completed or failed (see ton-balance skill). User can ask to skip polling.

Send Jetton (Token)

If user mentions a token by name, call get_known_jettons (see ton-balance skill) to find the jettonAddress
Call get_jetton_balance to verify sufficient balance
Call build_jetton_transfer with the jettonAddress, toAddress, and amount to build the transaction (it is NOT sent)
Preview it with emulate_transaction using the returned transaction.messages (recommended before broadcasting)
Ask one short yes/no confirmation before sending
Broadcast with send_raw_transaction passing the transaction.messages and transaction.fromAddress (jetton messages target the sender's jetton wallet)
Poll get_transaction_status until completed or failed

Notes

Amounts are human-readable (e.g., "1.5" = 1.5 GRAM (ex. TON), "100" = 100 tokens)
build_ton_transfer/build_jetton_transfer build the transaction only; send_raw_transaction is the tool that actually signs and broadcasts
Use emulate_transaction to preview expected balance changes before broadcasting (fake signature)
Always confirm with the user before broadcasting a transfer; prefer the host client's structured confirmation UI when available, otherwise accept natural-language yes/no and do not require a fixed confirmation phrase
After broadcasting, poll get_transaction_status by default. User can specify whether to check status.
If no wallet is configured, use the ton-create-wallet skill first

---name: ton-senddescription: Send GRAM (ex. TON) or jettons (tokens) to an address or TON DNS domain. Use when the user wants to send GRAM (ex. TON), transfer tokens, send jettons, pay someone, send funds to a .ton or .t.me domain, or transfer assets on the TON blockchain.---# Send GRAM (ex. TON) & TokensTransfer GRAM (ex. TON) or jettons to any address. Supports TON DNS resolution for `.ton` and `.t.me` domains.## MCP Tools| Tool | Required | Optional || ---- | -------- | -------- || `build_ton_transfer` | `toAddress`, `amount` | `comment`, `walletSelector` || `build_jetton_transfer` | `toAddress`, `jettonAddress`, `amount` | `comment`, `walletSelector` || `emulate_transaction` | `messages` | `validUntil` || `send_raw_transaction` | `messages` | `validUntil`, `fromAddress`, `walletSelector` || `resolve_dns` | `domain` | — || `back_resolve_dns` | `address` | — |`build_ton_transfer` and `build_jetton_transfer` do NOT broadcast — they return ready-to-send `transaction.messages` plus `transaction.fromAddress`. Preview with `emulate_transaction`, then broadcast with `send_raw_transaction`.## Workflows### Send GRAM (ex. TON)1. If the user provides a DNS name (e.g., `foundation.ton`, `user.t.me`) instead of a raw address, call `resolve_dns` first2. Call `build_ton_transfer` with address and amount to build the transaction (it is NOT sent)3. Preview it with `emulate_transaction` using the returned `transaction.messages` (recommended before broadcasting)4. Ask one short yes/no confirmation that restates the amount and recipient5. Broadcast with `send_raw_transaction` passing the `transaction.messages` and `transaction.fromAddress`6. Poll `get_transaction_status` with the returned `normalizedHash` until status is `completed` or `failed` (see `ton-balance` skill). User can ask to skip polling.### Send Jetton (Token)1. If user mentions a token by name, call `get_known_jettons` (see `ton-balance` skill) to find the `jettonAddress`2. Call `get_jetton_balance` to verify sufficient balance3. Call `build_jetton_transfer` with the `jettonAddress`, `toAddress`, and `amount` to build the transaction (it is NOT sent)4. Preview it with `emulate_transaction` using the returned `transaction.messages` (recommended before broadcasting)5. Ask one short yes/no confirmation before sending6. Broadcast with `send_raw_transaction` passing the `transaction.messages` and `transaction.fromAddress` (jetton messages target the sender's jetton wallet)7. Poll `get_transaction_status` until completed or failed## Notes- Amounts are human-readable (e.g., `"1.5"` = 1.5 GRAM (ex. TON), `"100"` = 100 tokens)- `build_ton_transfer`/`build_jetton_transfer` build the transaction only; `send_raw_transaction` is the tool that actually signs and broadcasts- Use `emulate_transaction` to preview expected balance changes before broadcasting (fake signature)- Always confirm with the user before broadcasting a transfer; prefer the host client's structured confirmation UI when available, otherwise accept natural-language yes/no and do not require a fixed confirmation phrase- After broadcasting, poll `get_transaction_status` by default. User can specify whether to check status.- If no wallet is configured, use the `ton-create-wallet` skill first

Frequently asked questions