sui-mcp-server

transfer_objects

Send one or more digital assets from your wallet to any address on the Sui blockchain by specifying object IDs and recipient.

Instructions

Transfer one or more objects to a recipient address.

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>",
      "objectIds": "<objectIds>"
    },
    "name": "transfer_objects"
  }
}

Input Schema

Name	Required	Description
`fromWallet`	Yes	Sending wallet name
`toAddress`	Yes	Recipient address
`objectIds`	Yes	Object IDs to transfer

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.3May 28, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, and the description fails to disclose behavioral traits like gas fees, authorization requirements, success conditions, or reversibility. For a transfer tool, these are critical gaps.

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?

The description is a single clear sentence with no extraneous information, well-structured and front-loaded.

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?

With no output schema, the description should mention what the tool returns (e.g., transaction digest). It also omits prerequisites like wallet ownership of objects. The minimal description leaves significant gaps.

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

Parameters3/5

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

Schema description coverage is 100%, so the description does not need to add much; baseline is 3. The description mentions 'one or more objects' which aligns with the array type but adds no extra semantics beyond 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?

The description clearly states the action (transfer), the resource (one or more objects), and the target (recipient address). It adequately distinguishes from sibling tools like transfer_sui which transfers SUI coins.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as transfer_sui, merge_coins, or split_coins. The description only states the function without usage context.

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

Deploy Server