sui-mcp-server

sui_get_function

Retrieve the full signature of a Move function, including type parameters, argument types, return types, and visibility. Use this to prepare for transaction simulation or PTB construction.

Instructions

Get the signature of a specific Move entry/public function — type parameters, argument types, return types, visibility. Use this before calling sui_simulate_transaction or constructing a PTB.

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": {
      "package_id": "<package_id>",
      "module_name": "<module_name>",
      "function_name": "<function_name>"
    },
    "name": "sui_get_function"
  }
}

Input Schema

Name	Required	Description
`package_id`	Yes
`module_name`	Yes
`function_name`	Yes
`network`	No	Sui network. Defaults to the server's configured default.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 23, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It states the tool returns signature details but does not mention whether it is read-only, idempotent, or requires authentication. For a query tool, this is a notable lack of transparency about safety and cost.

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 sentence that efficiently conveys the tool's output and a key use case. It contains no filler or redundant information, earning its place.

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 four parameters, no output schema, and no annotations, the description is sparse. It does not cover the return format, error handling, or prerequisites. For a tool used in a workflow (before simulation), more completeness is needed to handle edge cases or validation.

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

Parameters2/5

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

The input schema has 75% of parameters without descriptions (only 'network' has one). The description does not explain 'package_id,' 'module_name,' or 'function_name,' relying on domain knowledge. With low schema coverage, the description should compensate but fails to add meaning beyond the tool's purpose.

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 tool gets the signature of a Move function, listing specific details (type parameters, argument types, return types, visibility). It distinguishes from siblings like sui_get_package by focusing on function signatures, and provides a concrete use case (before sui_simulate_transaction or PTB construction).

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

Usage Guidelines4/5

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

The description explicitly says 'Use this before calling sui_simulate_transaction or constructing a PTB,' which guides the agent on when to invoke it. It does not include negative examples or alternative tools, but the usage context is clear and sufficient given the sibling list.

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