gate-info-tokenonchain

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 ./references/gate-runtime-rules.md

→ Also read ./references/info-news-runtime-rules.md for gate-info / gate-news shared rules (tool degradation, report standards, security, and output standards).

• Only call MCP tools explicitly listed in this skill. Tools not documented here must NOT be called, even if they

exist in the MCP server.

> Token On-Chain Analysis Skill (current version: no Smart Money). For token-level holder distribution, activity, and large transfers, call on-chain + basic coin info tools in parallel, then aggregate into a structured report.

Trigger Scenarios: User asks about token on-chain data, holder distribution, on-chain activity, large transfers, on-chain chip analysis, etc.

MCP Dependencies

Required MCP Servers

MCP Tools Used

Query Operations (Read-only)

• info_onchain_get_token_onchain
• info_coin_get_coin_info

Authentication

• API Key Required: No
• Credentials Source: None; this skill uses read-only Gate Info / Gate News MCP access only.

Installation Check

• Required: Gate-Info
• Install: Use the local Gate MCP installation flow for the current host IDE before continuing.
• Continue only after the required Gate MCP server is available in the current environment.

Routing Rules

Execution Workflow

Step 0: Multi-Dimension Intent Check

• Token-level on-chain → this Skill.
• Specific address (not token) → gate-info-addresstracker.
• Fundamentals + technicals + news together → gate-info-research (if available).

Step 1: Intent Recognition & Parameter Extraction

• symbol (required): Token ticker (e.g., BTC, ETH, SOL)
• chain (optional): e.g., eth, sol, bsc
• scope: one or more of holders, activity, transfers (smart_money — not available)
• time_range (optional): default 24h for transfers/activity

Step 2: Call MCP Tools in Parallel

Step 3: LLM Aggregation

• Contextualize on-chain data with coin info
• Identify patterns and anomalies
• Avoid speculative price predictions

Report Template

## {symbol} On-Chain Analysis

> Generated: {timestamp} | Chain: {chain or "All supported chains"}
> Note: Smart Money analysis not yet available in this version.

### Token Overview

| Metric | Value |
|--------|-------|
| Token | {symbol} ({name}) |
| Market Cap | ${market_cap} |
| Circulating Supply | {circulating_supply} |

### Holder Distribution (if scope includes holders)

{Tables + LLM concentration assessment}

### On-Chain Activity (if scope includes activity)

{Metrics + LLM trend assessment}

### Large Transfers (if scope includes transfers)

{Table + LLM flow assessment}

### On-Chain Health Score

{Dimensions scored /10 + overall}

### Key Insights

{2–3 data-driven bullets}

> On-chain data does not predict future prices. This does not constitute investment advice.

Decision Logic

Error Handling

Cross-Skill Routing

Safety Rules

1. No fabricated on-chain data: Only report MCP-returned data.
2. Address privacy: Shorten addresses (e.g., 0x1234...abcd); do not doxx.
3. No trading signals: Informational only; not buy/sell advice.
4. Exchange labels: Best-effort; may be mislabeled.
5. Data lag: Note indexing delays where relevant.
6. Smart Money: Clearly state unavailability rather than approximating.
7. Age & eligibility: Intended for users aged 18 or above with full civil capacity in their jurisdiction.
8. Data flow: The host agent processes user prompts; this skill directs read-only Gate-Info MCP tools listed above. The LLM summarizes tool output. This skill does not invoke additional third-party data services.