sui-mcp-server

transfer_sui

Transfer SUI from a managed wallet to a recipient Sui address. Provide the sending wallet, recipient address, and amount in SUI.

Instructions

Transfer SUI from a managed wallet to a recipient address. Amount is in SUI (not MIST).

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": {
      "fromWallet": "<fromWallet>",
      "toAddress": "<toAddress>",
      "amount": "<amount>"
    },
    "name": "transfer_sui"
  }
}

Input Schema

Name	Required	Description
`fromWallet`	Yes	Name of the sending wallet
`toAddress`	Yes	Recipient Sui address
`amount`	Yes	Amount in SUI

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.3May 28, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the action without disclosing behavior such as permission requirements, reversibility, or error conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no wasted words. The first sentence states the purpose, the second clarifies a critical unit detail. Perfectly concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Lacks any explanation of return values, prerequisites, or side effects. For a mutation tool without annotations, the description is insufficient for an agent to fully understand the operation's context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds value by clarifying that the amount parameter is in SUI, not MIST, preventing unit confusion. Other parameters are adequately described in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the action (Transfer), the resource (SUI from managed wallet to recipient), and distinguishes from siblings like transfer_objects by specifying the asset type and unit.

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 a helpful hint that amount is in SUI (not MIST), but lacks explicit guidance on when to use this tool versus alternatives like transfer_objects or other trade-related tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server