Gate Info MCP

info_platformmetrics_get_platform_history

Read-onlyIdempotent

Daily TVL, volume, and fees time series for one named protocol. One-shot profile→get_platform_info. Ranked multi-protocol list→search_platforms. CEX perps history: pass exchange_slug (e.g. gate) or platform_name. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.

Input Schema

TableJSON Schema

Name	Required	Description
`metrics`	No	tvl\|volume\|fees\|revenue\|volume_perps; default [tvl] when empty. volume_perps returns series when present in platform_history (GAP-001).
`end_date`	No	End YYYY-MM-DD.
`start_date`	No	Start YYYY-MM-DD.
`granularity`	No	day\|week\|month\|quarter; used for volume_perps field mapping in derivatives history index; default day.
`exchange_slug`	No	DWS exchange_slug (e.g. gate); optional if platform_name is set.
`platform_name`	No	Protocol or platform display name; optional if exchange_slug is set. For volume_perps, expanded to DWS exchange_slug-style keys (e.g. Gate.io→gate) like merge path.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`items`	Yes
`total`	Yes
`metrics`	Yes
`end_date`	Yes
`start_date`	Yes
`duration_ms`	Yes
`platform_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed4 schema fields changedApr 22, 2026

addedInput schema / properties / exchange_slug

Added value: +{
+  "description": "DWS exchange_slug (e.g. gate); optional if platform_name is set.",
+  "type": "string"
+}

addedInput schema / properties / granularity

Added value: +{
+  "description": "day|week|month|quarter; used for volume_perps field mapping in derivatives history index; default day.",
+  "type": "string"
+}

changedInput schema / properties / platform_name / description

Previous value: -"Protocol or platform name."New value: +"Protocol or platform display name; optional if exchange_slug is set. For volume_perps, expanded to DWS exchange_slug-style keys (e.g. Gate.io→gate) like merge path."

removedInput schema / required
```
Removed value: -[
-  "platform_name"
-]
```

Changed1 schema field changedApr 21, 2026

changedInput schema / properties / metrics / description

Previous value: -"tvl|volume|fees|revenue; default [tvl] when empty."New value: +"tvl|volume|fees|revenue|volume_perps; default [tvl] when empty. volume_perps returns series when present in platform_history (GAP-001)."

First observedApr 16, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark read-only and idempotent. Description adds extra context: 'Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.' This goes beyond the annotation flags and clarifies side-effect and security implications.

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 packs essential information into a few sentences: purpose, alternatives, CEX perps handling, and read-only nature. No fluff or repetition, highly efficient.

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 tool's complexity (6 parameters, output schema), the description provides sufficient context: it states what the output is (time series), how to select a protocol (exchange_slug or platform_name), when to use alternatives, and emphasizes safe read-only behavior. Output schema is separately provided, so no missing critical 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?

Schema covers 100% of parameters with descriptions. The description adds nuance beyond schema: 'volume_perps returns series when present in platform_history (GAP-001)' and clarifies the exchange_slug/platform_name relationship. This enriches parameter understanding without redundancy.

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?

Description clearly states the tool returns daily TVL, volume, and fees time series for one named protocol, and explicitly distinguishes it from get_platform_info (profile) and search_platforms (ranked list). This leaves no ambiguity about the resource and operation.

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?

Explicitly says when to use this tool versus alternatives: 'One-shot profile→get_platform_info. Ranked multi-protocol list→search_platforms.' Also specifies CEX perps history requires exchange_slug or platform_name, providing clear selection criteria.

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.