Gate Info MCP

info_platformmetrics_get_platform_info

Read-onlyIdempotent

One-shot protocol profile by name and scope. scope=full adds competition_metrics{} for CEX venues (spot/derivs/depth/OI core+extended/PoR). Set include_oi_symbol_detail=true with oi_symbol_limit (1-100, default 20) for top-N OI breakdown. Ranked multi-protocol list→search_platforms. Daily time 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

Name	Required	Description
`scope`	No	basic (default)\|with_chain_breakdown (adds tvl_by_chain, volume_by_chain)\|full (adds history_30d, top_pools, competition_metrics).
`platform_name`	Yes	Protocol or platform name.
`oi_symbol_limit`	No	Effective only when include_oi_symbol_detail=true. Default 20, range 1-100; >100 returns invalid_param.
`include_oi_symbol_detail`	No	scope=full only. true returns competition_metrics.oi_symbol_detail[] sorted by OI USD desc; default false.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`items`	Yes
`scope`	Yes
`total`	Yes
`duration_ms`	Yes
`platform_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 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"
+]
```

Changed3 schema fields changedMay 12, 2026

addedInput schema / properties / include_oi_symbol_detail

Added value: +{
+  "description": "scope=full only. true returns competition_metrics.oi_symbol_detail[] sorted by OI USD desc; default false.",
+  "type": "boolean"
+}

addedInput schema / properties / oi_symbol_limit

Added value: +{
+  "description": "Effective only when include_oi_symbol_detail=true. Default 20, range 1-100; >100 returns invalid_param.",
+  "type": "integer"
+}

changedInput schema / properties / scope / description

Previous value: -"basic (default)|with_chain_breakdown (adds tvl_by_chain, volume_by_chain)|full (adds history_30d, top_pools)."New value: +"basic (default)|with_chain_breakdown (adds tvl_by_chain, volume_by_chain)|full (adds history_30d, top_pools, competition_metrics)."

First observedApr 16, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description goes beyond annotations by stating the tool is read-only, provides public research data, involves no account access, order placement, or fund transfers, and is not investment advice. This aligns with the readOnlyHint and idempotentHint annotations and adds meaningful safety context.

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 brief, front-loaded with the core purpose, and uses compact separate statements for conditions and limitations. No redundant or filler wording is 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 the schema and annotations, the description is fully sufficient. It covers the tool's purpose, parameter behavior, safety profile, and relationship to sibling tools, with no apparent missing context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already covers 100% of parameter descriptions, so the baseline is 3. The description adds useful context by explaining the purpose of oi_symbol_limit as 'top-N OI breakdown' and clarifying scope-dependent behavior, slightly exceeding the schema alone.

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 returns a protocol profile by name and scope. It distinguishes itself from sibling tools by explicitly referencing search_platforms for ranked lists and get_platform_history for daily time series.

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 explains when to use optional parameters (scope=full, include_oi_symbol_detail=true) and provides cross-tool guidance for list and time-series needs. This gives an agent clear direction on selecting this tool over alternatives.

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.