Gate Info MCP

info_coin_search_coins

Read-onlyIdempotent

Multi-row asset list by category, chain, cap, type. One clear match→get_coin_info. Boards→get_coin_rankings. 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 filter: canonical name or alias (ETH→Ethereum, BSC→BNB Chain); contains match on normalized chain list.
`limit`	No	Page size; default 20, max 400.
`offset`	No	Offset; default 0.
`sort_by`	No	market_cap (default) \| fdv \| circulating_supply; all desc
`category`	No	Controlled sector tag or group (e.g. Layer 1, DEX); case-insensitive; matches category_type_flat then category_type; unknown values return empty list.
`asset_type`	No	crypto (default) \| tradefi \| all
`market_cap_max`	No	Max market cap USD.
`market_cap_min`	No	Min market cap USD; range on market_value / market_cap.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	No
`count`	Yes
`items`	Yes
`limit`	No
`total`	Yes
`offset`	No
`sort_by`	No
`category`	No
`asset_type`	No
`duration_ms`	Yes
`total_count`	Yes
`market_cap_max`	No
`market_cap_min`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedAug 27, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- changedInput schema / properties / market_cap_max / type
```
Previous value: -"number"New value: +[
+  "null",
+  "number"
+]
```
- changedInput schema / properties / market_cap_min / type
```
Previous value: -"number"New value: +[
+  "null",
+  "number"
+]
```
- 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 / market_cap_max / type
```
Previous value: -"number"New value: +[
+  "null",
+  "number"
+]
```
- changedOutput schema / properties / market_cap_min / type
```
Previous value: -"number"New value: +[
+  "null",
+  "number"
+]
```
First observedApr 16, 2026

TDQS

A4.5/5.0

Behavior4/5

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

While annotations already mark this as read-only and non-destructive, the description adds useful behavioral context: it is public research data, involves no account access, no order placement, and no fund transfers. This goes beyond the annotation hints 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 compact and front-loaded with the main purpose in the first sentence. Every sentence adds distinct information, and there is no redundant or filler content.

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 the rich schema and read-only annotations, the description provides sufficient context: it names alternatives, states side-effect-free behavior, and clarifies non-investment-advice status. No critical context appears missing for a list-search tool.

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 provides complete descriptions for all 8 parameters, including defaults and matching behavior, so the description adds little beyond mapping the high-level filter concepts (category, chain, cap, type) to the parameter set. Baseline 3 is appropriate since schema coverage is 100%.

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 states a specific purpose: returning a multi-row asset list filterable by category, chain, cap, and type. It also distinguishes siblings by directing one clear match to get_coin_info and board-style results to get_coin_rankings, making the tool's role clear.

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?

It explicitly names alternative tools and the conditions for using them ('One clear match→get_coin_info. Boards→get_coin_rankings.'), giving direct when-to-use/not-use guidance. The read-only and no-order caveats also clarify appropriate usage.

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.