sui-mcp-server

get_dynamic_fields

Retrieve dynamic fields from a Sui object by providing its parent ID. Control the number of fields returned with an optional limit.

Instructions

Get dynamic fields of an object.

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": {
      "parentId": "<parentId>"
    },
    "name": "get_dynamic_fields"
  }
}

Input Schema

Name	Required	Description	Default
`parentId`	Yes	Parent object ID
`limit`	No	Max fields to return (default: 50)

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, and the description does not disclose any behavioral traits such as read-only status, rate limits, pagination behavior, or error conditions. The presence of a 'limit' parameter hints at pagination but is not explained.

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 sentence with no superfluous words. It is concise, though it could be slightly expanded to improve clarity without losing efficiency.

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?

Given the lack of an output schema and the simplicity of the tool, the description does not explain what 'dynamic fields' are or what the return format looks like. It is insufficient for an agent to fully understand the tool's behavior and output.

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?

With 100% schema description coverage, the baseline is 3. The description adds no additional meaning beyond the param names and types, though it correctly reflects the required parameter.

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 verb 'Get' and the resource 'dynamic fields of an object,' making the tool's purpose unambiguous. It distinguishes itself from siblings like 'get_object' and 'get_move_struct' by targeting a specific sub-resource.

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_object' or 'multi_get_objects.' There is no mention of prerequisites, exclusions, or typical use cases.

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

Deploy Server