Skip to main content
Glama
0xfreak0

sui-analytics-mcp

by 0xfreak0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Enable tool profiles

enable_tools
Read-only

Enable additional Sui tool profiles for this session. When a needed tool is disabled, activate it by specifying its profile (forensics, developer, market, or all).

Instructions

Turn on more Sui tool profiles for this session. When a tool you need is not in your list, call this first: it is disabled, not missing. Do not rebuild a tool by hand. Pass profile or profiles: one name, several, or 'all'. Enabled tools are callable at once.

'forensics' (incident investigation: tracing, attribution, clustering, packages, labels, case findings): resolve_protocol_packages, sample_control_addresses, trace_funds, trace_flow_graph, find_flow_path, resolve_bridge_transfer, find_funding_source, find_funding_sources, get_address_fanout, classify_deposit_address, screen_address, 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, get_upgrade_history, manage_labels, query_events, check_activity, get_top_holders, compare_oracle_price, analyze_attack_tx, summarize_incident_losses, summarize_address_flows, aggregate_events, save_finding, list_findings, export_case, delete_finding, watch_addresses, poll_watch, get_nft_sales 'developer' (Move packages, bytecode, upgrades, PTBs, unsigned transactions, MVR): get_package_dependency_graph, 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' (DeepBook, pools, token search, validators): deepbook_orderbook, deepbook_trades, get_pool_stats, search_token, get_coin_info, get_validators On: core.

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?

Annotations declare readOnlyHint=true and openWorldHint=false. The description adds context by explaining the session-level effect: 'Enabled tools are callable at once.' It also warns against rebuilding tools manually, which is behavioral guidance. It does not contradict annotations and provides additional useful context beyond the simple read-only flag.

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. It front-loads the core instruction and trigger condition, then explains parameter usage, and finally lists the profiles with their tools. Each sentence serves a purpose, though the tool lists make it verbose. The structure is logical and scannable, so it earns a 4 rather than a 3.

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?

For a meta-tool with multiple profiles and many sub-tools, the description is comprehensive. It covers when to use it, how to use it, what each profile includes, and the immediate effect (tools become callable). No output schema exists, and the description appropriately explains the outcome. Nothing critical is missing for an agent to correctly invoke it.

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 the schema already includes descriptions for both `profile` and `profiles`, the description goes far beyond by enumerating the exact tools available under each profile (e.g., forensics, developer, market). This mapping is not present in the schema and gives the agent the ability to decide which profile to enable based on the needed tool. This adds substantial semantic value beyond the schema's basic 'profile to enable' note.

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 tool's purpose: 'Turn on more Sui tool profiles for this session.' It distinguishes itself from the sibling read/data tools by being a meta-tool that enables other tools. It also clarifies the context ('when a tool you need is not in your list'), making it unambiguous what it does and when it applies.

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 gives explicit usage guidance: 'When a tool you need is not in your list, call this first: it is disabled, not missing. Do not rebuild a tool by hand.' It also specifies how to pass parameters ('Pass `profile` or `profiles`: one name, several, or 'all''). This clearly tells the agent when to invoke this tool and how to use it, with no ambiguity.

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