Skip to main content
Glama
0xfreak0

sui-analytics-mcp

by 0xfreak0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

enable_tools

Activate missing Sui analytics tools by enabling a profile (core, forensics, developer, market, or all) for this session, making the needed capabilities immediately callable.

Instructions

Turn on additional Sui tool profiles for this session. This server ships a small default tool surface and keeps the rest one call away. Call this FIRST whenever the capability you need is not in your current tool list — the tool probably exists and is simply disabled. Do not reimplement a listed tool by hand.

'core' — Everyday lookups — wallets, balances, transactions, tokens, NFTs, DeFi positions. Tools: identify_address, get_wallet_overview, get_transaction, get_transactions, get_transaction_history, query_transactions, get_object, list_owned_objects, get_balance, analyze_token, get_token_prices, list_nfts, list_nft_collections, get_defi_positions, get_staking_summary, find_pools, resolve_name, get_chain_info 'forensics' — Incident investigation — fund tracing, batch funding attribution, address fan-out, live wallet-edge clustering, package analysis, multi-address timelines, object provenance, address labels, cross-chain bridge resolution, oracle-vs-market deviation, and recording findings into an exportable case report. Tools: resolve_protocol_packages, sample_control_addresses, trace_funds, resolve_bridge_transfer, find_funding_source, find_funding_sources, get_address_fanout, build_wallet_edges, analyze_multisig, find_shared_multisig, check_coin_restrictions, analyze_package, get_package, get_move_function, disassemble_module, build_timeline, trace_object_history, manage_labels, query_events, check_activity, get_top_holders, compare_oracle_price, aggregate_events, save_finding, list_findings, export_case, delete_finding 'developer' — Move package analysis — modules, disassembly, decompilation, upgrade diffing, dependency graphs, PTB decoding, unsigned transaction building, Move Registry. Tools: get_package, get_move_function, get_package_dependency_graph, analyze_package, disassemble_module, decompile_module, diff_package_upgrade, decode_ptb, simulate_transaction, build_transfer, build_staking, get_checkpoint, list_dynamic_fields, mvr_resolve, mvr_reverse_resolve, mvr_get_package_info, mvr_search, mvr_resolve_struct 'market' — Market data — DeepBook order book and fills, pool stats, token search, validators. Tools: deepbook_orderbook, deepbook_trades, get_pool_stats, search_token, get_coin_info, get_validators

Use 'all' for everything. Newly enabled tools are callable immediately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileNoProfile to enable, or 'all'. Accepts several: ['forensics','developer'].
profilesNoAlias for `profile`. Same values; use whichever reads better.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.12.1
    • changedInput schema / properties / profile / anyOf
      Previous value: -[
-  {
-    "enum": [
-      "core",
-      "forensics",
-      "developer",
-      "market"
-    ],
-    "type": "string"
-  },
-  {
-    "const": "all",
-    "type": "string"
-  }
-]New value: +[
+  {
+    "anyOf": [
+      {
+        "enum": [
+          "core",
+          "forensics",
+          "developer",
+          "market"
+        ],
+        "type": "string"
+      },
+      {
+        "const": "all",
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "items": {
+      "$ref": "#/properties/profile/anyOf/0"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / profile / description
      Previous value: -"Profile to enable, or 'all'."New value: +"Profile to enable, or 'all'. Accepts several: ['forensics','developer']."
    • addedInput schema / properties / profiles
      Added value: +{
+  "$ref": "#/properties/profile",
+  "description": "Alias for `profile`. Same values; use whichever reads better."
+}
    • removedInput schema / required
      Removed value: -[
-  "profile"
-]
  2. First observedv1.5.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains the session-scoped effect ("for this session"), the lazy-enablement model, and the consequence ("Newly enabled tools are callable immediately"). It does not describe the return value or what happens if a profile is already enabled, but the core behavioral traits are clearly disclosed.

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 well-structured: purpose, usage rule, then a consistent profile-by-profile layout ending with the 'all' shortcut and immediate availability. The forensics profile's prose is somewhat dense and lists many capabilities in a run-on style, but the overall structure is navigable and front-loaded with the most important guidance.

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?

Given the tool's meta-purpose and minimal schema, the description is complete: it explains when to call it, what each parameter value grants, which tools become available, and that effects are immediate. No output schema exists, but the outcome of calling this tool is the availability of other tools, which is fully stated. There are no missing details an agent would need to use it correctly.

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

Parameters5/5

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

Although schema coverage is 100%, the schema only says "Profile to enable, or 'all'." The description adds substantial semantic value by enumerating each profile ('core', 'forensics', 'developer', 'market'), describing its domain, listing the exact tools it enables, and clarifying the special value 'all'. It also explains the alias relationship by saying the `profiles` parameter takes the same values.

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: "Turn on additional Sui tool profiles for this session." It also clarifies what the tool is not by explaining that the server "ships a small default tool surface and keeps the rest one call away," which distinguishes it from the individual lookup tools listed as siblings.

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?

Usage guidance is explicit: "Call this FIRST whenever the capability you need is not in your current tool list — the tool probably exists and is simply disabled." It also warns against an incorrect alternative behavior: "Do not reimplement a listed tool by hand." This is direct, actionable, and leaves no ambiguity about when to invoke the tool.

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