Gate Info MCP

info_onchain_get_token_onchain

Read-onlyIdempotent

Token scope: holders, transfers, activity, smart_money. Address ledger→get_address_transactions. One tx→get_transaction. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.

Input Schema

TableJSON Schema

Name	Required	Description
`chain`	No	Chain; omit for service default.
`scope`	No	holders\|activity\|transfers\|smart_money\|full; default full.
`token`	Yes	Token symbol e.g. ETH, USDT, or contract address.
`upstream_raw_mode`	No	off (default) \| lite \| full. Prefer off for public MCP. include_upstream_raw=true forces full.
`include_upstream_raw`	No	Prefer false (default). If true, include explorer_*_page raw and transfer source_raw; large payload, not for public clients.

Output Schema

TableJSON Schema

Name	Required	Description
`chain`	Yes
`scope`	Yes
`token`	Yes
`holders`	No
`sources`	No
`activity`	No
`transfers`	No
`token_info`	No
`duration_ms`	Yes	required
`smart_money`	No
`data_quality`	No
`quality_reasons`	No
`explorer_token_raw`	No
`explorer_holders_raw`	No
`explorer_transfers_raw`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed29 schema fields changedAug 27, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedOutput schema / additionalProperties
```
Added value: +false
```
addedOutput schema / properties / activity / additionalProperties
```
Added value: +false
```

changedOutput schema / properties / activity / type

Previous value: -"object"New value: +[
+  "null",
+  "object"
+]

addedOutput schema / properties / duration_ms / description
```
Added value: +"required"
```

removedOutput schema / properties / explorer_holders_raw / anyOf

Removed value: -[
-  {
-    "type": "object"
-  },
-  {
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / explorer_holders_raw / items

Added value: +{
+  "maximum": 255,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / explorer_holders_raw / type
```
Added value: +[
+  "null",
+  "array"
+]
```

removedOutput schema / properties / explorer_token_raw / anyOf

Removed value: -[
-  {
-    "type": "object"
-  },
-  {
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / explorer_token_raw / items

Added value: +{
+  "maximum": 255,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / explorer_token_raw / type
```
Added value: +[
+  "null",
+  "array"
+]
```

removedOutput schema / properties / explorer_transfers_raw / anyOf

Removed value: -[
-  {
-    "type": "object"
-  },
-  {
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / explorer_transfers_raw / items

Added value: +{
+  "maximum": 255,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / explorer_transfers_raw / type
```
Added value: +[
+  "null",
+  "array"
+]
```
addedOutput schema / properties / holders / additionalProperties
```
Added value: +false
```
changedOutput schema / properties / holders / properties / top_holders / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```

changedOutput schema / properties / holders / type

Previous value: -"object"New value: +[
+  "null",
+  "object"
+]

changedOutput schema / properties / quality_reasons / type

Previous value: -"array"New value: +[
+  "null",
+  "array"
+]

addedOutput schema / properties / smart_money / additionalProperties
```
Added value: +false
```

changedOutput schema / properties / smart_money / type

Previous value: -"object"New value: +[
+  "null",
+  "object"
+]

addedOutput schema / properties / sources / items / additionalProperties
```
Added value: +false
```
changedOutput schema / properties / sources / items / properties / code / type
```
Previous value: -"integer"New value: +[
+  "null",
+  "integer"
+]
```

changedOutput schema / properties / sources / type

Previous value: -"array"New value: +[
+  "null",
+  "array"
+]

addedOutput schema / properties / token_info / additionalProperties
```
Added value: +false
```

changedOutput schema / properties / token_info / type

Previous value: -"object"New value: +[
+  "null",
+  "object"
+]

addedOutput schema / properties / transfers / additionalProperties
```
Added value: +false
```
changedOutput schema / properties / transfers / properties / large_transfers / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
changedOutput schema / properties / transfers / properties / supply_history / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```

changedOutput schema / properties / transfers / type

Previous value: -"object"New value: +[
+  "null",
+  "object"
+]

Changed2 schema fields changedAug 7, 2026

changedInput schema / properties / include_upstream_raw / description

Previous value: -"If true, include explorer_*_page raw and transfer source_raw; large payload. Default false."New value: +"Prefer false (default). If true, include explorer_*_page raw and transfer source_raw; large payload, not for public clients."

changedInput schema / properties / upstream_raw_mode / description

Previous value: -"off (default) | lite (row source_raw) | full (page + row). include_upstream_raw=true forces full."New value: +"off (default) | lite | full. Prefer off for public MCP. include_upstream_raw=true forces full."

First observedApr 16, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable context beyond that: 'Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.' This reinforces the read-only nature and clarifies boundaries (no account access, no trading), which is useful for an agent deciding whether to call it. It does not contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise – four short sentences that front-load the core purpose (token scope), then give alternatives, then safety disclaimers. Every sentence earns its place, with no filler or redundancy.

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?

Given the 5-parameter schema with 100% coverage and an output schema, the description covers essential usage context: it states the data scopes, points to alternatives, and clarifies the read-only, non-advice nature. It doesn't explain return format, but the output schema covers that. It also doesn't detail behavior like pagination or rate limits, but those aren't critical for a read-only research tool. Overall, it provides enough context for correct selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters (chain, scope, token, upstream_raw_mode, include_upstream_raw). The description adds little beyond repeating scope names (holders, transfers, activity, smart_money) that are already in the scope property's description. It doesn't elaborate on param formats or defaults beyond what the schema provides, so the baseline 3 is appropriate.

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 'Token scope' and enumerates the specific data types (holders, transfers, activity, smart_money), making it unambiguous what the tool returns. It also distinguishes itself by pointing to sibling tools for address-ledger and single-transaction queries, so an agent can tell it apart without opening the schema.

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?

Provides explicit alternates: 'Address ledger→get_address_transactions' and 'One tx→get_transaction'. This tells the agent when NOT to use this tool and which sibling to use instead. The 'Token scope' prefix clarifies that this is for token-level queries, not general on-chain address queries.

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

All Gate Info MCP tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool targets a distinct data object and action (e.g., coin info vs rankings, market snapshot vs batch, marketdetail kline vs markettrend kline), with prefixes and descriptions clearly separated by domain. No two tools appear to serve the same purpose.

Naming Consistency5/5

All tools follow a consistent pattern: info_<domain>_<verb>_<object>, with verbs mainly get, search, and batch. The naming style is uniform across all 32 tools, making it easy to infer tool purpose from its name.

Tool Count3/5

32 tools is heavy compared to typical servers, and it exceeds the 25-tool threshold. However, the server is a comprehensive crypto data aggregator covering multiple subdomains (coin, macro, market, onchain, platform metrics), which justifies the large count to some extent. It sits at the borderline between borderline and too many.

Completeness5/5

The tool surface covers the full lifecycle for read-only research: coin discovery, rankings, search, technical analysis, onchain exploration, platform metrics, stablecoins, yield pools, bridges, and macro indicators. No critical missing functionality for the stated purpose of public research data access.

info_onchain_get_token_onchain

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources