Gate Info MCP

info_coin_get_coin_rankings

Read-onlyIdempotent

Boards: popular, gainers/losers, twitter_hot, airdrop, new_listing, market_pulse_hot. time_range only for gainers/losers. Single match→get_coin_info. Filtered list→search_coins. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Rows; default 20, max 400.
`time_range`	No	Only for top_gainers\|top_losers: 1h\|24h (default)\|7d. Omit for other ranking_type or validation fails.
`listing_from`	No	new_listing only: Unix seconds from; 0 = omit.
`ranking_type`	Yes	popular\|top_gainers\|top_losers\|twitter_hot\|airdrop\|new_listing\|market_pulse_hot
`listing_query`	No	new_listing only: exchange / keyword for upstream query.
`listing_tickers`	No	new_listing only: comma tickers e.g. BTC,ETH.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`items`	Yes
`total`	Yes
`time_range`	Yes
`duration_ms`	Yes
`ranking_type`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedAug 27, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- 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"
+]
```
- changedOutput schema / properties / time_range / type
```
Previous value: -"string"New value: +[
+  "null",
+  "string"
+]
```

Changed1 schema field changedJun 9, 2026

changedInput schema / properties / ranking_type / description

Previous value: -"popular|top_gainers|top_losers|twitter_hot|airdrop|new_listing"New value: +"popular|top_gainers|top_losers|twitter_hot|airdrop|new_listing|market_pulse_hot"

First observedApr 16, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, open-world, and non-destructive. The description adds useful context by stating 'Read-only public research data', 'No account access', 'No order placement or fund transfers', and 'Not investment advice', which goes beyond the annotation flags without contradicting them.

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 highly compact, using terse bullet-style clauses and arrows to convey board types, parameter constraints, tool alternatives, and safety caveats. No unnecessary words or redundant elaboration are present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that an output schema is provided, the description covers the essential context: purpose, board categories, parameter restrictions, alternative tools, and behavioral boundaries. Nothing needed for correct invocation is missing.

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 already provides 100% parameter description coverage, including enum-like values for ranking_type and conditional notes for time_range and new_listing-specific fields. The description mostly repeats those constraints, so it adds little semantic value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The title 'Get Coin Rankings' and the enumerated board types clearly indicate the tool returns ranking lists, and the 'Single match→get_coin_info' / 'Filtered list→search_coins' lines distinguish it from sibling tools. However, the description never directly states 'retrieves ranked coin lists', relying on implication rather than an explicit purpose statement.

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?

The description explicitly names when to use this tool versus alternatives: 'Single match→get_coin_info' and 'Filtered list→search_coins'. It also gives parameter usage guidance ('time_range only for gainers/losers'), making the selection and invocation conditions clear.

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.