sui-mcp-server

get_move_function

Retrieve details of a specific Move function by specifying package ID, module name, and function name. Ideal for inspecting Sui blockchain smart contracts.

Instructions

Get details of a specific Move function.

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": {
      "packageId": "<packageId>",
      "moduleName": "<moduleName>",
      "functionName": "<functionName>"
    },
    "name": "get_move_function"
  }
}

Input Schema

Name	Required	Description
`packageId`	Yes	Package object ID
`moduleName`	Yes	Module name
`functionName`	Yes	Function name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.3May 28, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description alone must disclose behavior. It only says 'Get details', without specifying what details are returned, whether the call has side effects, or any authorization requirements. The agent lacks crucial behavioral information.

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

Conciseness4/5

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

The description is a single, efficient sentence. It is front-loaded with the core purpose. However, it could include more detail without being verbose. No wasted words, but slightly under-specified.

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?

There is no output schema, so the description should explain what 'details' encompasses. It fails to describe return values, pagination, or error conditions. For a 3-parameter tool with no annotations, the description is insufficient for an agent to fully understand usage.

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?

All three parameters (packageId, moduleName, functionName) are documented in the input schema with clear descriptions. The description adds no additional meaning beyond the schema. With 100% schema coverage, a score of 3 is appropriate.

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's action: 'Get details of a specific Move function.' It specifies the verb 'Get' and the resource 'Move function', distinguishing it from sibling tools like get_move_struct or get_normalized_module. The purpose is unambiguous.

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 versus alternatives such as get_normalized_module or get_move_struct. There is no mention of required prerequisites, context, or exclusions. The description is purely functional 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