Gate Info MCP

info_marketsnapshot_get_market_snapshot

Read-onlyIdempotent

One-symbol market snapshot: realtime price, a short kline clip, and project summary. Inputs include symbol, timeframe, source (e.g. spot), quote, and scope. When no data exists for the symbol, returns status=not_found with empty realtime/kline/project_info. Read-only public market data. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.

Input Schema

TableJSON Schema

Name	Required	Description
`quote`	No	Quote currency mapped to OpenSearch market; default USDT.
`scope`	No	Response field scope; default basic (trimmed). Allowed: basic\|detailed\|full.
`source`	No	Market source; default spot. futures is accepted and normalized to future. Allowed: alpha\|spot\|future\|futures\|fx.
`symbol`	Yes	Symbol e.g. BTC, ETH, USDC.
`timeframe`	No	Kline interval; wins over indicator_timeframe when both set; default 1h if both empty. Allowed: 15m\|1h\|4h\|1d.
`indicator_timeframe`	No	Alias of timeframe when timeframe omitted. Allowed: 15m\|1h\|4h\|1d.

Output Schema

TableJSON Schema

Name	Required	Description
`kline`	Yes
`quote`	No
`scope`	No
`source`	Yes
`status`	No	not_found when no market/project data; not_available when symbol known but data temporarily missing; partial when some sections present; omit on full success.
`symbol`	Yes
`realtime`	Yes
`timeframe`	Yes
`derivatives`	No
`duration_ms`	Yes
`market_pulse`	No
`project_info`	Yes
`institutional_channel_summary`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 9, 2026

changedOutput schema / properties / status / description

Previous value: -"not_found when no market/project data for the symbol; omit on normal success."New value: +"not_found when no market/project data; not_available when symbol known but data temporarily missing; partial when some sections present; omit on full success."

Changed3 schema fields changedSep 8, 2026

addedOutput schema / properties / kline / properties

Added value: +{
+  "amt": {
+    "description": "Present when upstream provides it; type may be number or string."
+  },
+  "close_price": {
+    "description": "Present when upstream provides it; type may be number or string."
+  },
+  "deal_cnt": {
+    "description": "Present when upstream provides it; type may be number or string."
+  },
+  "high_price": {
+    "description": "Present when upstream provides it; type may be number or string."
+  },
+  "latest_price": {
+    "description": "Present when upstream provides it; type may be number or string."
+  },
+  "low_price": {
+    "description": "Present when upstream provides it; type may be number or string."
+  },
+  "open_price": {
+    "description": "Present when upstream provides it; type may be number or string."
+  },
+  "time": {
+    "description": "Present when upstream provides it; type may be number or string."
+  },
+  "volatility_30d": {
+    "description": "Present when upstream provides it; type may be number or string."
+  },
+  "volatility_7d": {
+    "description": "Present when upstream provides it; type may be number or string."
+  },
+  "volatility_90d": {
+    "description": "Present when upstream provides it; type may be number or string."
+  }
+}

addedOutput schema / properties / project_info / properties

Added value: +{
+  "ahr999": {
+    "description": "Present when upstream provides it; type may be number or string."
+  },
+  "altcoin_season_index": {
+    "description": "Present when upstream provides it; type may be number or string."
+  },
+  "dominance": {
+    "description": "Present when upstream provides it; type may be number or string."
+  },
+  "fdv": {
+    "description": "Present when upstream provides it; type may be number or string."
+  },
+  "fear_greed_index": {
+    "description": "Present when upstream provides it; type may be number or string."
+  },
+  "market_cap": {
+    "description": "Present when upstream provides it; type may be number or string."
+  }
+}

addedOutput schema / properties / realtime / properties

Added value: +{
+  "best_ask": {
+    "description": "Best ask when present."
+  },
+  "best_bid": {
+    "description": "Best bid when present."
+  },
+  "bid_ask_spread": {
+    "description": "Spread alias when present."
+  },
+  "high": {
+    "description": "Session/period high when present."
+  },
+  "highest_bid": {
+    "description": "Highest bid alias when present."
+  },
+  "last": {
+    "description": "Last price (canonical; aliases current_price/last_price/price are normalized into last)."
+  },
+  "low": {
+    "description": "Session/period low when present."
+  },
+  "lowest_ask": {
+    "description": "Lowest ask alias when present."
+  },
+  "price_change_24h": {
+    "description": "24h change (canonical)."
+  },
+  "spread": {
+    "description": "Bid-ask spread when present."
+  },
+  "tick": {
+    "description": "Optional tick object when present."
+  },
+  "trend_info": {
+    "description": "Optional trend label when present."
+  },
+  "update_time": {
+    "description": "Upstream update time when present."
+  },
+  "volume_24h": {
+    "description": "24h volume (canonical)."
+  }
+}

Changed9 schema fields changedSep 8, 2026

changedInput schema / properties / indicator_timeframe / description

Previous value: -"Alias of timeframe when timeframe omitted."New value: +"Alias of timeframe when timeframe omitted. Allowed: 15m|1h|4h|1d."

addedInput schema / properties / indicator_timeframe / enum
```
Added value: +[
+  "15m",
+  "1h",
+  "4h",
+  "1d"
+]
```

changedInput schema / properties / scope / description

Previous value: -"basic (default, trimmed)|detailed|full."New value: +"Response field scope; default basic (trimmed). Allowed: basic|detailed|full."

addedInput schema / properties / scope / enum

Added value: +[
+  "basic",
+  "detailed",
+  "full"
+]

changedInput schema / properties / source / description

Previous value: -"alpha|spot|futures (future)|fx; default spot."New value: +"Market source; default spot. futures is accepted and normalized to future. Allowed: alpha|spot|future|futures|fx."

addedInput schema / properties / source / enum

Added value: +[
+  "alpha",
+  "spot",
+  "future",
+  "futures",
+  "fx"
+]

addedInput schema / properties / symbol / minLength
```
Added value: +1
```

changedInput schema / properties / timeframe / description

Previous value: -"Kline: 15m|1h|4h|1d; wins over indicator_timeframe when both set; default 1h if both empty."New value: +"Kline interval; wins over indicator_timeframe when both set; default 1h if both empty. Allowed: 15m|1h|4h|1d."

addedInput schema / properties / timeframe / enum

Added value: +[
+  "15m",
+  "1h",
+  "4h",
+  "1d"
+]

Changed1 schema field changedSep 8, 2026

addedOutput schema / properties / status

Added value: +{
+  "description": "not_found when no market/project data for the symbol; omit on normal success.",
+  "type": "string"
+}

Changed11 schema fields changedAug 27, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedOutput schema / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / derivatives / additionalProperties
```
Added value: +true
```
- changedOutput schema / properties / derivatives / type
```
Previous value: -"object"New value: +[
+  "null",
+  "object"
+]
```
- addedOutput schema / properties / institutional_channel_summary / additionalProperties
```
Added value: +true
```
- changedOutput schema / properties / institutional_channel_summary / type
```
Previous value: -"object"New value: +[
+  "null",
+  "object"
+]
```
- addedOutput schema / properties / kline / additionalProperties
```
Added value: +true
```
- addedOutput schema / properties / market_pulse / additionalProperties
```
Added value: +true
```
- changedOutput schema / properties / market_pulse / type
```
Previous value: -"object"New value: +[
+  "null",
+  "object"
+]
```
- addedOutput schema / properties / project_info / additionalProperties
```
Added value: +true
```
- addedOutput schema / properties / realtime / additionalProperties
```
Added value: +true
```
Changed1 schema field changedJun 9, 2026
- addedOutput schema / properties / market_pulse
```
Added value: +{
+  "type": "object"
+}
```
Changed1 schema field changedMay 27, 2026
- addedOutput schema / properties / institutional_channel_summary
```
Added value: +{
+  "type": "object"
+}
```
Changed1 schema field changedApr 21, 2026
- addedOutput schema / properties / derivatives
```
Added value: +{
+  "type": "object"
+}
```
First observedApr 16, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description adds behavioral context beyond the annotations: it clarifies no account access, no order placement or fund transfers, and explicitly says 'not investment advice.' It also discloses the not_found behavior with empty fields for realtime/kline/project_info. Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds specific edge-case behavior, making it a 4.

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 four sentences with no redundancy. It front-loads the core purpose and scope, then quickly covers special case behavior and disclaimers. Every sentence earns its place; it's appropriately sized for the tool's complexity.

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?

The description is complete for this tool. It covers what the tool does, its key inputs, the not_found behavior, and its limitations (read-only, no account access). Since the output schema exists separately, the description doesn't need to explain return values. Nothing essential is missing for an agent to call it correctly.

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?

Schema description coverage is 100%, so the baseline is 3. The description lists the inputs (symbol, timeframe, source, quote, scope) but adds no semantics beyond what the schema already provides; for example, it doesn't elaborate on how 'source' maps to enum values or how 'scope' affects response. This is exactly at the baseline: the schema already does the heavy lifting, and the description adds minimal extra meaning.

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's function: 'One-symbol market snapshot: realtime price, a short kline clip, and project summary.' This specifies the verb (get), the resource (market snapshot), and the scope (single symbol), and it distinguishes from siblings like batch_market_snapshot. An agent can understand what this tool does without opening the schema.

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?

The description implies usage context by naming the key inputs (symbol, timeframe, source, quote, scope) and clarifying it's a one-symbol snapshot with read-only public data. It does not explicitly reference alternative tools or provide 'when to use this instead of that' guidance, but the scope distinction from batch_market_snapshot is implicit. It could have named alternatives more directly, so it's a strong 4.

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.