Skip to main content
Glama

enable_tools

Activate the Sui tool profile you need—core, forensics, developer, or market—to expand available capabilities on the fly.

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_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, multi-address timelines, object provenance, address labels, oracle-vs-market deviation, and recording findings into an exportable case report. Tools: trace_funds, find_funding_source, find_funding_sources, get_address_fanout, 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
profileYesProfile to enable, or 'all'.
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses session scoping ('for this session'), that newly enabled tools are callable immediately, and explains the default tool surface. It does not address idempotency or error behavior, but the disclosed context is valuable.

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-organized with clearly labeled profiles and tool lists. The tool lists are necessary for choosing the right profile and each section earns its place. It is front-loaded with the key instruction.

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 relatively simple tool with one parameter and no output schema, the description is complete: it explains purpose, profiles, and when to use. It could mention the return value or confirmation behavior, but it is not critical given the tool's simplicity.

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?

The schema only provides the parameter description 'Profile to enable, or all.' The description enriches this significantly by explaining each profile and listing its constituent tools, making the parameter meaning far clearer than schema alone.

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 states a clear verb+resource: 'Turn on additional Sui tool profiles for this session.' It clearly distinguishes itself from sibling tools (which are actual data lookup tools) by explaining that this is a meta-tool for enabling more tools.

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?

Explicit when-to-use guidance: '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 advises against reimplementation and details what each profile contains, guiding profile selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/0xfreak0/sui-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server