Skip to main content
Glama
0xfreak0

sui-analytics-mcp

by 0xfreak0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get object

get_object
Read-only

Fetch a Sui object by ID to reveal its type, owner, version, content, and digest, plus NFT metadata and current balances or kiosk controller.

Instructions

Get a Sui object by its ID. Returns type, owner, version, content (JSON), and digest. Automatically extracts display metadata (name, description, image_url) for NFTs. For the LATEST version it also lists address_balances (funds the object holds in its own address balance, which are not among its fields and which only its defining module can withdraw) and, for a kiosk, kiosk_cap_holder: who actually controls it today, since content.owner is self-declared and not kept in sync with the KioskOwnerCap transfer that does. Neither is read for a specific version: both are current state and would misname a past snapshot's controller.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkNoNetwork: 'mainnet' (default) | 'testnet' | 'devnet'
versionNoSpecific version to fetch
object_idYesThe object ID (0x...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.20.0
    • changedInput schema / properties / network / description
      Previous value: -"Which Sui network to run this call against: 'mainnet' (default), 'testnet', or 'devnet'. Set this per-call — different tool calls in the same session can target different networks (e.g. to compare a value on testnet against mainnet)."New value: +"Network: 'mainnet' (default) | 'testnet' | 'devnet'"
  2. First observedv1.5.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses important behavioral nuances: it extracts NFT display metadata, adds address_balances and kiosk_cap_holder on latest version only, and warns that content.owner is self-declared and not kept in sync with actual KioskOwnerCap transfers. This is exactly the kind of context an agent needs to interpret results correctly.

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 front-loaded with the core purpose and return fields, then adds precise caveats about version-sensitive data. Every sentence earns its place; the length is justified by the non-obvious behavior around address_balances and kiosk_cap_holder.

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

Completeness5/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 carries the burden of explaining return values, and it does so thoroughly: type, owner, version, content, digest, display metadata, and the version-dependent extra fields. It also covers the tricky current-state vs. historical-version distinction. Nothing essential is missing for an agent to invoke and interpret this tool correctly.

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

Parameters4/5

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

The input schema already documents all three parameters with 100% coverage, so the baseline is 3. The description adds extra meaning for the version parameter by explaining that extra fields are only present for the latest version and that current-state fields should not be read for historical versions. This goes beyond the schema's minimal 'Specific version to fetch.'

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 opens with a specific verb and resource: 'Get a Sui object by its ID.' It clearly distinguishes itself from sibling tools like list_owned_objects or get_transactions by focusing on fetching a single object and enumerating its returned fields.

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 gives clear context for when to call this tool: when you have a Sui object ID and want its details. It also explains the version-dependent behavior, telling the agent that address_balances and kiosk_cap_holder are only meaningful for the latest version. It does not explicitly name alternatives or exclusion criteria, but the usage context is strong.

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