Skip to main content
Glama

Gate Info MCP

by io.github.gateio-dev
OverviewDiscussionsAdmin

info_platformmetrics_search_platforms

Read-onlyIdempotent

Ranked multi-protocol list with filter and sort. One-shot profile→get_platform_info. One named protocol daily series→get_platform_history. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoChain filter.
limitNoRows; default 20, max 400.
sort_byNotvl|volume_24h|volume_spot_24h|volume_perps_24h|volume_perps_7d|volume_perps_30d|volume_perps_qtd|fees_24h; default tvl.
sort_orderNoasc|desc; default desc. When CEX + sort_by volume_perps_* uses the HF derivatives sub-index only, ranking follows this order; response echoes the normalized value.
platform_typeNoOptional filter on platform_info.platform_type. Empty or all = no filter. dex|dexs|dexes map to DEX+Dexs; derivatives|cex as labeled; defi expands to DeFi TVL group; any other value is passed through to the index (e.g. Lending, CDP, Yield).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainYes
countYes
itemsYes
limitYes
totalYes
sort_byYes
sort_orderNo
duration_msYes
platform_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / sort_order
      Added value: +{
+  "description": "asc|desc; default desc. When CEX + sort_by volume_perps_* uses the HF derivatives sub-index only, ranking follows this order; response echoes the normalized value.",
+  "type": "string"
+}
    • addedOutput schema / properties / sort_order
      Added value: +{
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / platform_type / description
      Previous value: -"DEX|Dexs|Derivatives|CEX|all (empty same as all). Other values rejected."New value: +"Optional filter on platform_info.platform_type. Empty or all = no filter. dex|dexs|dexes map to DEX+Dexs; derivatives|cex as labeled; defi expands to DeFi TVL group; any other value is passed through to the index (e.g. Lending, CDP, Yield)."
  4. Changed1 schema field changed
    • changedInput schema / properties / platform_type / description
      Previous value: -"DEX|Dexs|Derivatives|all (empty same as all). Other values rejected."New value: +"DEX|Dexs|Derivatives|CEX|all (empty same as all). Other values rejected."
  5. Changed2 schema fields changed
    • changedInput schema / properties / platform_type / description
      Previous value: -"CEX|DEX|Lending|Bridge|Yield|Derivatives|..."New value: +"DEX|Dexs|Derivatives|all (empty same as all). Other values rejected."
    • changedInput schema / properties / sort_by / description
      Previous value: -"tvl|volume_24h|volume_spot_24h|volume_perps_24h|fees_24h; default tvl."New value: +"tvl|volume_24h|volume_spot_24h|volume_perps_24h|volume_perps_7d|volume_perps_30d|volume_perps_qtd|fees_24h; default tvl."
  6. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The description clearly states 'Read-only public research data. No account access, no order placement or fund transfers. Not investment advice,' which goes beyond the readOnly and openWorld annotations by specifying access and safety characteristics. There is no contradiction with the annotations.

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

Conciseness4/5

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

The description is concise and each sentence adds information, but the arrow-phrased references ('One-shot profile→get_platform_info') are somewhat cryptic and could be more readable. Overall length is appropriate and no filler is present.

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 that an output schema is present and parameters are fully covered by the schema, the description sufficiently covers purpose, behavior, and key alternative tools. It does not describe output shape, but that is not required when the output schema is available.

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?

All five parameters are already described with 100% schema coverage, including detailed mapping for platform_type and sort_order behavior. The top-level description adds only generic 'filter and sort' context, not additional parameter-specific meaning, so it meets the baseline but does not exceed it.

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 'Ranked multi-protocol list with filter and sort,' which clearly identifies the tool as a search/list operation for platforms and distinguishes it from detail/history tools by explicitly referencing get_platform_info and get_platform_history for one-shot profile and daily series use cases.

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?

It provides implicit usage guidance: use this tool for ranked multi-protocol lists with filter/sort, while pointing to get_platform_info for a single profile and get_platform_history for a single protocol's daily series. It could be more explicit about when to prefer this over other sibling tools, but the key alternatives are named.

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