Skip to main content
Glama
0xfreak0

sui-analytics-mcp

by 0xfreak0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List owned objects

list_owned_objects
Read-only

Retrieve raw objects owned by a Sui address, with optional type filter and pagination for efficient investigation of asset holdings and fund flows.

Instructions

List raw objects owned by a Sui address with optional type filter and pagination. For NFTs specifically, prefer list_nfts (resolves kiosk storage, extracts display metadata). For a wallet summary, prefer get_wallet_overview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 50, max 1000)
ownerNoOwner address (0x...). Required; `address` is accepted in its place.
cursorNoPagination cursor from previous response
addressNoAlias for `owner`.
networkNoNetwork: 'mainnet' (default) | 'testnet' | 'devnet'
object_typeNoFilter by object type (e.g. 0x2::coin::Coin<0x2::sui::SUI>)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.20.0
    • addedInput schema / properties / address
      Added value: +{
+  "description": "Alias for `owner`.",
+  "type": "string"
+}
    • addedInput schema / properties / limit / maximum
      Added value: +1000
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • 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'"
    • changedInput schema / properties / owner / description
      Previous value: -"Owner address (0x...)"New value: +"Owner address (0x...). Required; `address` is accepted in its place."
    • removedInput schema / required
      Removed value: -[
-  "owner"
-]
  2. First observedv1.5.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already mark the tool as read-only, so the bar for behavioral transparency is lower. The description adds useful context by noting that this tool lists 'raw' objects and does not resolve kiosk storage or extract display metadata, which sets expectations beyond the structured annotations.

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 only two sentences with no filler. The core function is front-loaded in the first sentence, and the alternative routing is packed efficiently into the second. Every sentence earns its place.

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

Completeness4/5

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

For a read-only listing tool with a complete schema, the description covers the essential purpose, filtering, pagination, and alternatives. It does not describe the return shape, but the absence of an output schema and the presence of full parameter descriptions make this acceptable.

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 schema fully documents all parameters including owner, address alias, limit, cursor, network, and object_type. The description mentions 'optional type filter and pagination' but does not add meaningful detail beyond the schema, so 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?

The description clearly states the verb 'List' and resource 'raw objects owned by a Sui address,' and explicitly differentiates from list_nfts and get_wallet_overview. This allows an agent to distinguish the tool from sibling tools at a glance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit routing guidance: use list_nfts for NFTs and get_wallet_overview for wallet summaries, implying list_owned_objects is for general raw object queries. This directly tells the agent when to use this tool versus alternatives.

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