Skip to main content
Glama

Gate Info MCP

by io.github.gateio-dev
OverviewDiscussionsAdmin

info_marketsnapshot_batch_market_snapshot

Read-onlyIdempotent

Batch market snapshots for up to 20 symbols; raw array length 1–20 before trim/dedupe; missing symbols appear in not_found. Same timeframe/source/quote/scope semantics as the single-symbol snapshot. 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
NameRequiredDescriptionDefault
quoteNoQuote currency; default USDT; maps to OpenSearch market.
scopeNoResponse field scope; default basic. Allowed: basic|detailed|full.
sourceNoMarket source; default spot. futures is accepted and normalized to future. Allowed: alpha|spot|future|futures|fx.
symbolsYesRaw symbol array length 1–20 (checked before trim/dedupe). Then trim, reject blanks, dedupe; missing symbols go to not_found (omitted from items).
timeframeNoKline interval; default 1h when omitted. Allowed: 15m|1h|4h|1d.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
itemsYes
quoteNo
scopeNo
totalYes
sourceNo
symbolsNo
not_foundYes
timeframeNo
unavailableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / symbols / description
      Previous value: -"Symbol list (1–20 after trim/dedupe). Missing symbols yield empty rows; the batch still succeeds."New value: +"Raw symbol array length 1–20 (checked before trim/dedupe). Then trim, reject blanks, dedupe; missing symbols go to not_found (omitted from items)."
    • changedInput schema / properties / symbols / type
      Previous value: -[
-  "null",
-  "array"
-]New value: +"array"
    • addedOutput schema / properties / unavailable
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "reason": {
+        "type": "string"
+      },
+      "retryable": {
+        "type": "boolean"
+      },
+      "symbol": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "symbol",
+      "reason",
+      "retryable"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}
    • changedOutput schema / required
      Previous value: -[
-  "total",
-  "count",
-  "items",
-  "not_found"
-]New value: +[
+  "total",
+  "count",
+  "items",
+  "not_found",
+  "unavailable"
+]
  2. Changed1 schema field changed
    • addedOutput schema / properties / items / items / properties
      Added value: +{
+  "kline": {
+    "additionalProperties": true,
+    "description": "Same shape as get_market_snapshot.kline.",
+    "properties": {
+      "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."
+      }
+    },
+    "type": "object"
+  },
+  "project_info": {
+    "additionalProperties": true,
+    "description": "Same shape as get_market_snapshot.project_info.",
+    "properties": {
+      "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."
+      }
+    },
+    "type": "object"
+  },
+  "quote": {
+    "type": "string"
+  },
+  "realtime": {
+    "additionalProperties": true,
+    "description": "Same shape as get_market_snapshot.realtime.",
+    "properties": {
+      "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)."
+      }
+    },
+    "type": "object"
+  },
+  "scope": {
+    "type": "string"
+  },
+  "source": {
+    "type": "string"
+  },
+  "status": {
+    "description": "not_found when empty; omit on success.",
+    "type": "string"
+  },
+  "symbol": {
+    "type": "string"
+  },
+  "timeframe": {
+    "type": "string"
+  }
+}
  3. Changed9 schema fields changed
    • changedInput schema / properties / scope / description
      Previous value: -"Response scope."New value: +"Response field scope; default basic. Allowed: basic|detailed|full."
    • addedInput schema / properties / scope / enum
      Added value: +[
+  "basic",
+  "detailed",
+  "full"
+]
    • changedInput schema / properties / source / description
      Previous value: -"spot (default)|futures (future)|alpha|fx."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"
+]
    • changedInput schema / properties / symbols / description
      Previous value: -"Symbol list, max 20. Missing symbols yield empty rows; the batch still succeeds."New value: +"Symbol list (1–20 after trim/dedupe). Missing symbols yield empty rows; the batch still succeeds."
    • addedInput schema / properties / symbols / maxItems
      Added value: +20
    • addedInput schema / properties / symbols / minItems
      Added value: +1
    • changedInput schema / properties / timeframe / description
      Previous value: -"Kline: 15m|1h|4h|1d; default 1h."New value: +"Kline interval; default 1h when omitted. Allowed: 15m|1h|4h|1d."
    • addedInput schema / properties / timeframe / enum
      Added value: +[
+  "15m",
+  "1h",
+  "4h",
+  "1d"
+]
  4. Changed2 schema fields changed
    • removedOutput schema / properties / duration_ms
      Removed value: -{
-  "type": "integer"
-}
    • changedOutput schema / required
      Previous value: -[
-  "total",
-  "count",
-  "items",
-  "not_found",
-  "duration_ms"
-]New value: +[
+  "total",
+  "count",
+  "items",
+  "not_found"
+]
  5. Changed7 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / symbols / 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 / not_found / type
      Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
    • changedOutput schema / properties / symbols / type
      Previous value: -"array"New value: +[
+  "null",
+  "array"
+]
  6. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description adds important operational details: raw array validation length, missing symbols routed to not_found, and safety disclaimers (no order placement, not investment advice). This gives the agent a richer behavioral model for edge cases. No contradiction with annotations; rather, it complements them.

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, using three sentences with front-loaded purpose and necessary behavioral details. However, there is redundancy: 'Read-only public market data. Read-only public research data.' repeats virtually the same information, wasting a few words. Overall, it is efficient but not perfectly trimmed, so 4.

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 output schema exists (so return format is covered structurally), the description provides all essential context: batch limit, validation behavior, missing symbol handling, and safety guarantees. The agent has enough to call the tool correctly without ambiguity. No missing operational details that would cause incorrect invocation.

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% (all parameters have descriptive text), so the baseline is 3. The description adds a cross-reference to single-symbol semantics, which helps interpret defaults and behavior, but it largely repeats the schema's explanation of the symbols array and missing symbol handling. The added value is marginal but non-zero, so a 3 is appropriate.

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 states a specific verb and resource: 'Batch market snapshots for up to 20 symbols' and differentiates from the single-symbol snapshot by noting 'Same timeframe/source/quote/scope semantics as the single-symbol snapshot.' This clearly distinguishes the tool from its sibling info_marketsnapshot_get_market_snapshot. The purpose is unambiguous and immediately actionable.

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 for fetching multiple snapshots at once and explicitly notes the read-only, batch nature. It does not name specific alternatives or state when not to use it, but the cross-reference to the single-symbol snapshot provides contextual guidance. This is clear context without explicit exclusions, matching the '4=clear context, no exclusions' level.

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