Skip to main content
Glama

Gate Info MCP

by io.github.gateio-dev
OverviewDiscussionsAdmin

info_marketsnapshot_get_market_overview

Read-onlyIdempotent

Broad market overview dashboard: capitalization, volume, dominance, and sentiment style metrics. No symbol required. Read-only public market breadth data. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ahr999Yes
btc_priceYes
updated_atYes
duration_msYes
btc_dominanceYes
eth_dominanceYes
fear_greed_indexYes
fear_greed_labelYes
total_market_capYesUSD total market cap; null when that upstream slice fails. Each field may be null independently.
total_volume_24hYes
active_coins_countYes
altcoin_season_indexYes
market_cap_change_24hYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties
      Removed value: -{}
    • addedOutput schema / additionalProperties
      Added value: +false
    • changedOutput schema / properties / active_coins_count / type
      Previous value: -"integer"New value: +[
+  "null",
+  "integer"
+]
    • changedOutput schema / properties / ahr999 / type
      Previous value: -"number"New value: +[
+  "null",
+  "number"
+]
    • changedOutput schema / properties / altcoin_season_index / type
      Previous value: -"integer"New value: +[
+  "null",
+  "integer"
+]
    • changedOutput schema / properties / btc_dominance / type
      Previous value: -"number"New value: +[
+  "null",
+  "number"
+]
    • changedOutput schema / properties / btc_price / type
      Previous value: -"number"New value: +[
+  "null",
+  "number"
+]
    • changedOutput schema / properties / eth_dominance / type
      Previous value: -"number"New value: +[
+  "null",
+  "number"
+]
    • changedOutput schema / properties / fear_greed_index / type
      Previous value: -"integer"New value: +[
+  "null",
+  "integer"
+]
    • changedOutput schema / properties / fear_greed_label / type
      Previous value: -"string"New value: +[
+  "null",
+  "string"
+]
    • changedOutput schema / properties / market_cap_change_24h / type
      Previous value: -"number"New value: +[
+  "null",
+  "number"
+]
    • changedOutput schema / properties / total_market_cap / type
      Previous value: -"number"New value: +[
+  "null",
+  "number"
+]
    • changedOutput schema / properties / total_volume_24h / type
      Previous value: -"number"New value: +[
+  "null",
+  "number"
+]
    • changedOutput schema / properties / updated_at / type
      Previous value: -"string"New value: +[
+  "null",
+  "string"
+]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly and idempotent annotations, the description adds concrete detail that it is public market breadth data with no account access, no order placement, no fund transfers, and not investment advice. This fully discloses behavior.

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 mostly concise and structured, but slightly redundant with 'Read-only public market breadth data' and 'Read-only public research data' saying similar things. Still, it remains focused and readable.

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

Completeness4/5

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

For a simple, parameterless overview tool, the description covers what data is included, that it is read-only public information, and key limitations. It does not detail output structure, but that is not required given the simplicity and existing annotations.

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 tool has no parameters and the input schema is empty, matching the baseline expectation for parameter-free tools. No additional parameter documentation is needed.

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 provides a broad market overview dashboard with capitalization, volume, dominance, and sentiment metrics. It distinguishes itself by explicitly noting no symbol is required, which separates it from symbol-specific market tools.

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 when to use it: for broad, symbol-free market aggregate data rather than individual asset or detailed market snapshots. It does not explicitly name alternative tools but the 'no symbol required' phrasing provides practical usage guidance.

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