Skip to main content
Glama
Sign In
sui-mcp-server

sui-mcp-server

by ExpertVagabond
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

split_coins

Split a coin into multiple coins with specified amounts in MIST. Useful for creating smaller denominations for payments.

Instructions

Split a coin into multiple coins with specified amounts (in 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": {
      "wallet": "<wallet>",
      "coinId": "<coinId>",
      "amounts": "<amounts>"
    },
    "name": "split_coins"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesWallet name
coinIdYesObject ID of the coin to split
amountsYesAmounts for each new coin (in MIST)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.3

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It implies mutation but does not disclose whether the original coin is destroyed, required permissions, or side effects. Lacks critical behavioral context.

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?

Single sentence that conveys the core action efficiently. No unnecessary words, front-loaded with key verb and resource.

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?

No output schema, yet description does not mention return values or post-condition. Missing details about whether original coin is consumed, which is important for a split operation.

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 coverage is 100%, so description adds minimal value beyond schema. It redundantly mentions 'in MIST' which is already in the amounts schema. Baseline score due to high coverage.

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 (split), resource (coin), and specifies amounts in MIST. It effectively distinguishes from sibling tools like merge_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 on when to use or not use this tool, no prerequisites or alternatives mentioned. The description does not help an agent decide between split_coins and other coin manipulation tools.

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

Deploy Server

Other Tools