MCP Sui Tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| faucetD | Get faucet from sui networks |
| sui-balanceC | Get balance of an address from sui networks |
| sui-transferC | transfer SUI(in mist) to single or multiple addresses |
| random-sui-accountB | Create random SUI account, do not use it in production. |
| gen_mnemonicC | Generate mnemonic(Not recommended for production) |
| gen_sui_accounts_by_mnemonicC | Create SUI accounts from mnemonic(Not recommended for production) |
| get_account_info_by_private_keyD | Get account info by private key |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
The tools have some overlap that could cause confusion, particularly between 'gen_mnemonic', 'gen_sui_accounts_by_mnemonic', and 'random-sui-account' which all relate to account generation with unclear boundaries. However, tools like 'faucet', 'sui-balance', and 'sui-transfer' have distinct purposes, and descriptions help differentiate them to some extent.
The naming is inconsistent with mixed conventions: 'faucet' and 'gen_mnemonic' use snake_case, 'gen_sui_accounts_by_mnemonic' uses snake_case with a verbose name, 'get_account_info_by_private_key' uses snake_case, 'random-sui-account' uses kebab-case, and 'sui-balance' and 'sui-transfer' use kebab-case. There is no discernible pattern, and the verb styles vary, making it chaotic.
With 7 tools, the count is well-scoped for the server's purpose of SUI blockchain operations. Each tool appears to earn its place by covering key functionalities like account management, balance checking, and transfers, without being overly heavy or thin for the domain.
The tool surface covers core SUI operations such as account creation, balance retrieval, and transfers, with no major dead ends. However, there are minor gaps, like missing tools for transaction history or smart contract interactions, which agents might need to work around but don't severely hinder basic workflows.