Skip to main content
Glama

Gate Info MCP

by io.github.gateio-dev
OverviewDiscussionsAdmin

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
NameRequiredDescriptionDefault
chainNoChain; omit for service default.
scopeNoholders|activity|transfers|smart_money|full; default full.
tokenYesToken symbol e.g. ETH, USDT, or contract address.
upstream_raw_modeNooff (default) | lite | full. Prefer off for public MCP. include_upstream_raw=true forces full.
include_upstream_rawNoPrefer false (default). If true, include explorer_*_page raw and transfer source_raw; large payload, not for public clients.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainYes
scopeYes
tokenYes
holdersNo
sourcesNo
activityNo
transfersNo
token_infoNo
duration_msYesrequired
smart_moneyNo
data_qualityNo
quality_reasonsNo
explorer_token_rawNo
explorer_holders_rawNo
explorer_transfers_rawNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed29 schema fields changed
    • 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"
+]
  2. Changed2 schema fields changed
    • 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."
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

The annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description goes beyond these by explicitly stating 'Read-only public research data' and enumerating prohibited actions (no account access, no order placement, no fund transfers). This reinforces and expands on the annotations, giving the agent a clear understanding of the tool's behavioral limits.

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 concise and well-structured. It starts with the primary purpose, then contrasts with related tools, and ends with behavioral disclaimers. Every sentence adds value and there is no redundancy or fluff. The structure aids quick comprehension.

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 an output schema (not shown in the description), so explaining return values is not necessary. The description covers the tool's purpose, scope, and limitations, and provides enough context for an agent to decide when to use it. The only minor gap is that it does not explicitly describe typical use cases or scenarios beyond general research, but this is not critical.

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?

The schema covers 100% of parameters with descriptive text (e.g., token symbol or contract address, scope options, upstream_raw_mode). The tool description itself does not add significant parameter-specific information beyond what is already in the schema. Baseline of 3 is appropriate given the high schema coverage, but the description adds little extra parameter semantics.

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 clearly states the tool's purpose: obtaining token on-chain data (holders, transfers, activity, smart_money). It distinguishes it from sibling tools like get_address_transactions and get_transaction by explicitly contrasting those use cases. This makes the tool's scope unambiguous and easy to differentiate.

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 provides explicit usage context: it is for read-only public research data and explicitly states what it is not for (no account access, no order placement, no fund transfers). It also hints at when to use alternative tools (address ledger, single transaction). While it doesn't explicitly say 'use this tool when...', the guidance is clear enough for an agent to select appropriately.

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 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources