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

sui-mcp-server

by ExpertVagabond
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

move_call

Execute a Move function call on Sui by specifying target (package::module::function), arguments, and type arguments. Requires a wallet for signing.

Instructions

Execute a Move function call. Arguments are passed as an array of strings/numbers.

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>",
      "target": "<target>"
    },
    "name": "move_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesWallet name for signing
targetYesMove call target: package::module::function
argumentsNoFunction arguments
typeArgumentsNoType arguments for generic functions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.3

TDQS

C2.9/5.0
Behavior2/5

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

Description only says 'Execute a Move function call' without disclosing side effects, state changes, gas requirements, or failure modes. No annotations exist to compensate.

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?

Extremely concise, one sentence front-loaded with the core action. No wasted words.

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?

For a transaction-submission tool with 4 parameters and no output schema, the description lacks information about return values, error handling, and usage context relative to siblings like dry_run_transaction.

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% with descriptions for each parameter. The description adds 'Arguments are passed as an array of strings/numbers', which clarifies format but adds limited meaning beyond the schema.

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

Purpose4/5

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

The description clearly states 'Execute a Move function call', identifying the verb and resource. It distinguishes from query siblings like get_move_function, but does not clarify that this is a transaction submission, which reduces differentiation.

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 this tool vs alternatives like dev_inspect or dry_run_transaction. No context about prerequisites or when this is appropriate.

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