| name | gate-dex-market |
| version | 2026.4.8-1 |
| updated | 2026-04-08 |
| description | On-chain DEX market data queries via Gate: token prices/价格, K-line/OHLC candlestick charts, token rankings, security risk audits, new token discovery, holder analysis, and trading volume stats. Read-only — no transactions. Use when the user asks for 'token price', 'price of ETH', 'check SOL price', '查价格', 'K线', 'candlestick', 'OHLC', 'top gainers', 'trending tokens', 'is this token safe', 'honeypot check', 'new tokens', 'trading volume', or 'liquidity events'. Do NOT use for swap/trade execution (use gate-dex-trade) or wallet balance/account queries (use gate-dex-wallet). |
Gate DEX Market
Pure Routing Layer — READ-ONLY data queries only. Never executes transactions. All specifications in references/.
General Rules
⚠️ STOP — You MUST read and strictly follow the shared runtime rules before proceeding.
Do NOT select or call any tool until all rules are read. These rules have the highest priority.
→ Read gate-runtime-rules.md
Trigger Scenarios: Use when the user wants to look up or analyze market data without executing any transaction:
- Price lookup: "what is the price of ETH", "check SOL price", "price of 0x1234..."
- Charts: "show K-line", "candlestick chart", "price trend"
- Rankings: "top gainers", "trending tokens", "token rankings"
- Security: "is this token safe", "security audit", "honeypot check", "risk analysis"
- Discovery: "new tokens", "newly listed", "holder analysis", "whale tracking"
- Volume: "trading volume", "buy-sell pressure", "liquidity events"
Project convention — MCP only
No OpenAPI unless user explicitly asks. MCP setup: see gate-dex-trade/references/setup.md.
NOT this skill (common misroutes):
- "quote for swapping X to Y" →
gate-dex-trade (swap execution)
- "check my balance" →
gate-dex-wallet (account query)
- "buy ETH" / "sell USDT" →
gate-dex-trade (transaction execution)
Routing Flow
User triggers market data query
|
Step 1: OpenAPI only if user explicitly asks. Else MCP only.
Step 2: MCP discovery → success = MCP mode; fail = MCP setup guide (no OpenAPI fallback).
Feature Matrix
| Feature | MCP | OpenAPI | Notes |
|---|
| K-line / Candlestick | Yes | Yes | |
| Token basic info | Yes | Yes | |
| Token rankings | Yes | Yes | |
| Security risk audit | Yes | Yes | |
| Tradable token list | Yes | Yes | |
| Cross-chain bridge tokens | Yes | No | MCP only |
| Holder analysis (Top N) | No | Yes | OpenAPI only |
| New token discovery | No | Yes | OpenAPI only |
| Liquidity events (Rug Pull) | No | Yes | OpenAPI only |
| Volume stats (multi-period) | No | Yes | OpenAPI only |
Mode Dispatch
MCP Mode
Read and strictly follow references/mcp.md, execute according to its complete workflow.
Includes: connection detection, 6 market data tools (dex_market_get_kline, dex_token_get_coin_info, dex_token_ranking, dex_token_get_risk_info, dex_token_list_swap_tokens, dex_token_list_cross_chain_bridge_tokens), no authentication required for market queries.
OpenAPI Mode (Progressive Loading)
Explicit user request only. Load files progressively:
- Always load first:
references/openapi/_shared.md — env detection, credentials, API call method (via helper script)
- Then load based on query type:
Legacy monolithic file preserved at references/openapi.md for backward compatibility.
Supported Chains
Actual supported chains are determined by runtime API/Resource returns:
- MCP Mode: via
dex_chain_config tool
- OpenAPI Mode: chain parameter in request
Common chains: eth, bsc, polygon, arbitrum, optimism, avax, base, sol.
Security Rules
- Data objectivity: Present prices and rankings objectively, no investment advice
- Risk warnings: Clearly remind users to judge investment risks themselves when showing security audits
- Credential security: Follow §3 of gate-runtime-rules.md for auth/credential handling
- Read-only: All operations are data queries, no on-chain write operations
