Skip to main content
Glama
0xfreak0

sui-analytics-mcp

by 0xfreak0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get transaction history

get_transaction_history
Read-only

Get decoded transaction history for any Sui wallet, including protocol actions and token flows. Paginate through newest or oldest transactions with cursor support.

Instructions

(Recommended for wallet activity) Get decoded transaction history for a Sui wallet: protocol names (e.g. Cetus, Suilend), action descriptions (e.g. 'Swap USDC → SUI') and token flow for each transaction. Newest first by default; order: 'oldest' starts from the address's first transaction instead. Each page reports its order and the oldest_shown/newest_shown timestamps; pass next_cursor back as cursor with the same order to continue. Rows are decoded from each transaction's complete balance changes and commands. address_poisoning is checked over the page shown, so the default page covers recent activity. Each row's subject_flow is the queried address's own signed balance change per coin, with formatted amounts and coin_verified; token_flow is the transaction sender's, so on a transfer this address received it shows the sender's outflow. counterparties names up to 25 addresses that received value in the row, with counterparty_count when there were more. Prefer this over query_transactions when exploring what a wallet has been doing. signed_as_alias, when present, lists transactions this address signed as an 0x2::address_alias delegate for another wallet; the page above cannot show them, because their sender is the other wallet. Which wallets name this address comes from a scan reused for up to five minutes, and alias_scan_as_of says when it read the chain. signed_as_alias_unavailable marks a scan that did not finish, including beside rows it did find.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of transactions to return (default 10, max 50)
orderNo'newest' (default) starts at the most recent transaction and pages back in time; 'oldest' starts at the first and pages forward.
cursorNo`next_cursor` from the previous page. Continues in the same direction; pass the same `order`.
addressYesSui wallet address (0x...)
networkNoNetwork: 'mainnet' (default) | 'testnet' | 'devnet'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.20.0
    • removedInput schema / properties / after
      Removed value: -{
-  "description": "Pagination cursor for next page",
-  "type": "string"
-}
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "`next_cursor` from the previous page. Continues in the same direction; pass the same `order`.",
+  "type": "string"
+}
    • 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'"
    • addedInput schema / properties / order
      Added value: +{
+  "description": "'newest' (default) starts at the most recent transaction and pages back in time; 'oldest' starts at the first and pages forward.",
+  "enum": [
+    "newest",
+    "oldest"
+  ],
+  "type": "string"
+}
  2. First observedv1.5.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only supply readOnlyHint=true and openWorldHint=true; the description adds substantial behavioral context beyond them: pagination mechanics (order, next_cursor, oldest_shown/newest_shown), address_poisoning check scope, the subject_flow vs token_flow distinction, counterparty truncation at 25, and the alias scan's 5-minute cache and incomplete-scan flag. No contradiction with annotations.

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 long, but it is front-loaded with the purpose and recommendation, then follows a logical flow (ordering, pagination, decoding, row fields, edge cases). Every sentence carries unique information for a complex tool with no output schema, so the length is earned rather than padded.

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?

With no output schema, the description carries the full burden of explaining return values, and it does so thoroughly: page metadata (order, timestamps, next_cursor), row semantics (subject_flow vs token_flow, counterparties, coin_verified), and edge cases (signed_as_alias, alias_scan_as_of, signed_as_alias_unavailable). Given the tool's complexity (5 parameters, no output schema), nothing needed for correct invocation is missing.

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?

Schema covers 100% of parameters so baseline is 3, but the description adds real semantic value beyond the schema: it explains that 'order: oldest' starts from the address's first transaction, and that next_cursor must be passed with the same order to continue. This clarifies cross-parameter dependency that the schema leaves implicit.

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 first sentence states a specific verb and resource ('Get decoded transaction history for a Sui wallet') and immediately lists the distinctive outputs (protocol names, action descriptions, token flow). It differentiates from siblings by emphasizing 'decoded' and explicitly pointing to query_transactions as the alternative, so an agent can tell them apart.

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 opens with '(Recommended for wallet activity)' and later states 'Prefer this over query_transactions when exploring what a wallet has been doing,' naming the specific sibling and the condition that selects this tool. This is explicit when-to-use guidance with an alternative named.

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