Skip to main content
Glama
0xfreak0

sui-analytics-mcp

by 0xfreak0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Analyze token

analyze_token
Read-only

Analyze a Sui token by symbol or coin type to retrieve metadata, current price, 24h change, total supply, and top 5 holders in one call.

Instructions

(Recommended for token research) Get a comprehensive analysis of a Sui token in one call: metadata, current price, 24h change, total supply, and top 5 holders. Accepts either a coin type (e.g. '0x2::sui::SUI') or a symbol (e.g. 'DEEP', 'cetus'). A symbol several coins use returns status ambiguous_symbol with candidates (verified first, then by supply) from a symbol index of every mainnet coin up to its sync date. A symbol more than 100 coins use returns its count and no candidates, since the index keeps only the count; a coin published after the sync date is found only by a bounded live scan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSymbol (e.g. 'USDC', 'deep') or full coin type (e.g. '0x2::sui::SUI'). A symbol is matched exactly; for a name or part of a symbol use search_token.
networkNoNetwork: 'mainnet' (default) | 'testnet' | 'devnet'
include_holdersNoInclude top 5 holders (default: true). Set false for faster response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.21.0
    • changedInput schema / properties / query / description
      Previous value: -"Token name, symbol (e.g. 'USDC', 'deep'), or full coin type (e.g. '0x2::sui::SUI')"New value: +"Symbol (e.g. 'USDC', 'deep') or full coin type (e.g. '0x2::sui::SUI'). A symbol is matched exactly; for a name or part of a symbol use search_token."
  2. Changed1 schema field changedv1.20.0
    • 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'"
  3. First observedv1.5.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses important edge-case behaviors: ambiguous symbols return candidates ordered by verification and supply, symbols covering more than 100 coins return only a count due to index limitations, and coins published after the sync date are found only by a bounded live scan. This is substantial behavioral context an agent needs to interpret results correctly.

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 front-loaded with purpose and then covers input formats and edge cases in a logical order. It is slightly dense but every sentence carries necessary information; no filler. A 5 would require even tighter phrasing, but this is well-structured for the complexity.

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?

The tool has no output schema, so the description must convey what the response contains; it lists the main data fields and the ambiguous_symbol/count outcomes. It does not detail error responses or how to use candidates, but the provided information is sufficient for an agent to decide whether to call it and how to interpret common results. A 5 would require a bit more on response handling.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful semantics for the query parameter by explaining how ambiguous symbols are resolved (candidate ordering), the >100-coin count-only behavior, and the sync-date/live-scan limitation. This goes beyond the schema's simple format description, justifying a 4.

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: 'Get a comprehensive analysis of a Sui token in one call' and enumerates the included data (metadata, price, 24h change, supply, top 5 holders). This clearly distinguishes it from price-only or balance-only siblings, and the 'Recommended for token research' label adds explicit intent.

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

Usage Guidelines4/5

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

The description marks the tool as recommended for token research and the schema description explicitly routes partial-name or symbol-part lookups to search_token. It does not enumerate when to prefer siblings like get_token_prices or get_balance, but the comprehensive-analysis scope and the one exclusion provide adequate usage guidance.

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