Gate Info MCP

info_markettrend_get_kline

Read-onlyIdempotent

Trend-index OHLCV for symbols, with optional indicator bundle. Exchange pair or contract candles, or fine intervals→marketdetail_get_kline. Columns→get_indicator_history. Chart-label snapshot→get_technical_analysis. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.

Input Schema

TableJSON Schema

Name	Required	Description
`size`	No	Row count; alias of limit; default 100, max 400.
`limit`	No	Row count; default 100, max 400; alternative to size.
`period`	No	Window: 1h\|4h\|24h\|7d\|3d\|5d\|10d; default 24h. Ignored when start/end set.
`symbol`	Yes	Symbol e.g. BTC, ETH.
`end_time`	No	Absolute end.
`timeframe`	Yes	Candle interval: 1m\|5m\|15m\|1h\|4h\|1d.
`start_time`	No	Absolute start: ms timestamp or ISO8601; wins over period when paired with end.
`with_indicators`	No	If true, include technical columns in _source; default OHLCV only.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`size`	Yes
`count`	Yes
`items`	Yes
`total`	Yes
`period`	Yes
`symbol`	Yes
`timeframe`	Yes
`duration_ms`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3/5.0

Behavior4/5

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

The description adds transparency beyond the annotations with statements like 'Read-only public research data' and 'No account access, no order placement or fund transfers,' which clarify the tool's safe, read-only nature. It does not contradict 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.

Conciseness2/5

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

The description is poorly structured, consisting of fragments and cryptic arrow references. It is not concise or easy to parse, reducing its clarity.

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

Completeness2/5

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

Although the output schema exists, the description does not sufficiently clarify the tool's purpose or its distinction from closely related siblings, leaving gaps in context for an agent.

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 descriptions for all parameters, so the baseline is 3. The tool description only adds a brief note about 'optional indicator bundle' (matching with_indicators) and does not significantly enhance parameter understanding.

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

Purpose3/5

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

The description states that the tool returns OHLCV data with optional indicators, but it does not clearly differentiate this tool from the sibling marketdetail_get_kline. The phrase 'Trend OHLCV' is ambiguous, and the references to alternative tools are cryptic.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description hints at alternatives with arrows (e.g., 'fine intervals→marketdetail_get_kline'), but it does not explicitly state when to use this tool versus the alternatives. The guidance is implicit and not fully actionable.

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.