Gate Info MCP

info_platformmetrics_get_liquidation_heatmap

Read-onlyIdempotent

Liquidation density by symbol and price buckets. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.

Input Schema

TableJSON Schema

Name	Required	Description
`range`	No	Price range or bucket spec.
`symbol`	Yes	Symbol e.g. BTC, ETH.
`exchange`	No	Exchange; empty = all venues.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`items`	Yes
`range`	Yes
`total`	Yes
`symbol`	Yes
`exchange`	Yes
`duration_ms`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedAug 27, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- 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

A3.8/5.0

Behavior4/5

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

Beyond the annotations indicating read-only and non-destructive behavior, the description explicitly states 'No account access, no order placement or fund transfers' and 'Not investment advice,' providing additional context about the tool's limitations and safety profile. This goes slightly beyond the annotations but does not fully describe all behavioral aspects.

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 concise, using only a few short sentences to convey purpose and safety disclaimers. It contains no redundant or unnecessary information, making it efficient and easy to parse.

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?

Given that the tool has an output schema (not shown here), the description does not need to explain return values. The description covers the core purpose and safety notes, providing sufficient context for an agent to understand what the tool does. It lacks some usage context but that is covered under usage guidelines.

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 descriptions for 'symbol', 'range', and 'exchange' provide basic meaning (e.g., 'Symbol e.g. BTC, ETH'), and the tool description does not elaborate further. Since schema coverage is 100%, this meets the baseline but adds no extra semantic clarity.

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 as returning liquidation density by symbol and price buckets. It is distinct from sibling tools by explicitly focusing on liquidation heatmap data, differentiating it from other market and platform metrics tools.

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

Usage Guidelines2/5

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

The description does not provide explicit guidance on when to use this tool versus alternatives. It does not mention potential use cases or contrast with other platform metrics tools, leaving the agent to infer appropriate usage from the tool name and description alone.

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.