Gate Info MCP

info_coin_get_coin_info

Read-onlyIdempotent

Look up one cryptocurrency profile by ticker, name, contract address, or Gate symbol. Optional chain disambiguates address clashes. Returns matching rows with basic project fields. Read-only public data; not investment advice.

Input Schema

TableJSON Schema

Name	Required	Description
`size`	No	Max rows; omit for default 3; minimum 1, maximum 20. Over-limit rejected (not truncated).
`chain`	No	Chain hint for address disambiguation when query_type=address or auto-detected EVM address; e.g. eth, tron, bsc.
`query`	Yes	Search text: symbol, contract address, localized name, etc. Non-empty.
`scope`	No	Response field scope; default basic when omitted. Allowed: basic\|detailed\|full\|with_project\|with_tokenomics.
`fields`	No	Field allowlist; empty = all. scope wins when both set.
`query_type`	No	Lookup mode; default auto when omitted. Allowed: auto\|address\|symbol\|name\|project\|gate_symbol\|source_id.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	No
`count`	Yes
`items`	Yes
`query`	Yes
`scope`	No
`total`	Yes
`query_type`	Yes
`duration_ms`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 8, 2026

addedOutput schema / properties / items / items / properties

Added value: +{
+  "category": {
+    "description": "Category label(s)."
+  },
+  "chain": {
+    "description": "Chain name or list of chains."
+  },
+  "contract_address": {
+    "description": "Contract address; null when native / unavailable."
+  },
+  "gate_symbol": {
+    "description": "Gate trading symbol when available."
+  },
+  "name": {
+    "description": "Display name string (not a JSON blob).",
+    "type": "string"
+  },
+  "source_id": {
+    "description": "Canonical project id; null when empty."
+  },
+  "symbol": {
+    "description": "Ticker symbol e.g. BTC.",
+    "type": "string"
+  }
+}

Changed10 schema fields changedSep 8, 2026

changedInput schema / properties / query / description

Previous value: -"Search text: symbol, contract address, localized name, etc."New value: +"Search text: symbol, contract address, localized name, etc. Non-empty."

addedInput schema / properties / query / minLength
```
Added value: +1
```

changedInput schema / properties / query_type / description

Previous value: -"auto (default) | address | symbol | name | project | gate_symbol | source_id"New value: +"Lookup mode; default auto when omitted. Allowed: auto|address|symbol|name|project|gate_symbol|source_id."

addedInput schema / properties / query_type / enum

Added value: +[
+  "auto",
+  "address",
+  "symbol",
+  "name",
+  "project",
+  "gate_symbol",
+  "source_id"
+]

changedInput schema / properties / scope / description

Previous value: -"basic (default) | detailed | full; with_project/with_tokenomics align with full _source."New value: +"Response field scope; default basic when omitted. Allowed: basic|detailed|full|with_project|with_tokenomics."

addedInput schema / properties / scope / enum

Added value: +[
+  "basic",
+  "detailed",
+  "full",
+  "with_project",
+  "with_tokenomics"
+]

addedInput schema / properties / size / default
```
Added value: +3
```

changedInput schema / properties / size / description

Previous value: -"Max rows; default 3, max 20. Values above max are rejected."New value: +"Max rows; omit for default 3; minimum 1, maximum 20. Over-limit rejected (not truncated)."

addedInput schema / properties / size / maximum
```
Added value: +20
```
addedInput schema / properties / size / minimum
```
Added value: +1
```

Changed2 schema fields changedSep 8, 2026

changedInput schema / properties / chain / description

Previous value: -"Chain hint for address disambiguation when query_type=address or auto-detected EVM address; e.g. eth, tron, bsc. Same normalization as search_coins."New value: +"Chain hint for address disambiguation when query_type=address or auto-detected EVM address; e.g. eth, tron, bsc."

changedInput schema / properties / size / description

Previous value: -"Max rows; default 3, max 20."New value: +"Max rows; default 3, max 20. Values above max are rejected."

Changed5 schema fields changedAug 27, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- changedInput schema / properties / fields / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
- addedOutput schema / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / items / items / additionalProperties
```
Added value: +true
```
- changedOutput schema / properties / items / type
```
Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
```
First observedApr 16, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description reinforces this with 'Read-only public data' while adding operational context: the optional chain 'disambiguates address clashes' and the response 'returns matching rows with basic project fields.' The 'not investment advice' disclaimer adds extra context beyond the structured annotations, and there is no contradiction.

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?

Three sentences with zero waste; the core purpose is front-loaded in the first sentence, and each subsequent sentence contributes new information (disambiguation behavior, return content, safety disclaimer). Every sentence earns its place.

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?

For a read-only lookup tool, the description covers purpose, lookup keys, clash-disambiguation behavior, and the nature of returns, while the 100%-coverage schema handles all parameter semantics and the output schema covers return shape. The only minor omission is explicit error/limit behavior, but the schema already documents over-limit rejection.

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 baseline of 3 applies — every parameter (query, size, chain, scope, fields, query_type) is already documented with defaults, enums, and constraints. The description adds modest value by mapping query_type modes to real-world lookup keys (ticker, name, contract address, Gate symbol), but it does not materially extend the schema's parameter documentation.

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?

States a specific verb and resource ('Look up one cryptocurrency profile') and enumerates the accepted lookup keys (ticker, name, contract address, Gate symbol). The singular 'one profile' and identifier-based framing distinguish it from siblings like info_coin_search_coins and info_coin_get_coin_rankings without ambiguity.

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

Usage Guidelines3/5

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

The description implies the tool is for targeted single-record lookups when an identifier is already known ('by ticker, name, contract address, or Gate symbol'), and the chain parameter guidance hints at the address-disambiguation case. However, it never explicitly names alternatives such as info_coin_search_coins or states when not to use this tool, leaving routing to inference.

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

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.