sui-mcp-server

sui_batch_get_objects

Fetch up to 50 Sui objects in a single round-trip, with individual per-object success or failure results. Use this instead of repeated sui_get_object calls for a known list of IDs.

Instructions

Fetch up to 50 objects in one round-trip. Returns per-object results (each may succeed or fail individually). Prefer this over a loop of sui_get_object when you have a known list of ids.

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": {
      "object_ids": "<object_ids>"
    },
    "name": "sui_batch_get_objects"
  }
}

Input Schema

Name	Required	Description
`object_ids`	Yes	Up to 50 object ids.
`source`	No
`network`	No	Sui network. Defaults to the server's configured default (usually mainnet).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 23, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. Mentions 'each may succeed or fail individually', which is important behavioral info. However, lacks details on error handling or rate limits.

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?

Two sentences, front-loaded with key information, no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complexity is low; description covers batch behavior and per-object results but does not explain return value structure beyond that. For a fetch tool with no output schema, it is adequate but not comprehensive.

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 67%, and the description adds little beyond schema (e.g., 'up to 50' is already in schema). Baseline 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?

Clearly states 'Fetch up to 50 objects in one round-trip' with a specific verb and resource. Distinguishes from sibling sui_get_object by suggesting preference over a loop.

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?

Explicitly states 'Prefer this over a loop of sui_get_object when you have a known list of ids', giving clear guidance on when to use. Could be more explicit about when not to use, but sufficient.

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