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

sui-mcp-server

by ExpertVagabond
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

multi_get_objects

Batch-fetch multiple blockchain objects by their IDs in a single call, with optional content and type inclusion.

Instructions

Batch-fetch multiple objects by their IDs in one call.

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": {
      "objectIds": "<objectIds>"
    },
    "name": "multi_get_objects"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectIdsYesArray of object IDs to fetch
showContentNoInclude content (default: true)
showTypeNoInclude type (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.3

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only says 'batch-fetch', which suggests a read-only operation, but does not disclose error handling (e.g., what happens if an ID is invalid), ordering of results, or any side effects. The lack of behavioral details is a significant gap.

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 with no extraneous words. It directly conveys the core purpose without redundancy, making it highly concise.

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?

For a simple batch query tool with 3 parameters and no output schema, the description captures the basic functionality. However, it lacks important context such as handling of missing IDs, result ordering, and performance implications of batching, which are needed for full completeness.

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 description coverage is 100%, so the parameters are well-documented there. The description adds no additional context beyond 'batch-fetch', but the schema already provides definitions for objectIds, showContent, and showType. Baseline is appropriate at 3.

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 action 'batch-fetch', the resource 'objects', and the method 'by their IDs in one call'. It distinguishes from the sibling tool 'get_object' by implying multiple objects at once.

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 implies use when fetching multiple objects by ID in a single call, differentiating from 'get_object'. However, it does not explicitly state when not to use it or mention alternatives for non-ID-based queries.

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