Gate Info MCP

info_marketdetail_get_recent_trades

Read-onlyIdempotent

Read-only recent Gate trade prints for a trading pair or contract. Inputs: symbol (required), market_type spot|futures|delivery|options (default spot), limit 1–400 (default 50; over-limit rejected), settle for futures (usdt|btc) or delivery (usdt). create_time_ms keeps upstream units (spot usually ms; futures/delivery often fractional seconds). side is optional (spot); derivatives may use signed size. Does not place orders. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Recent trades count; omit for default 50; minimum 1, maximum 400. Over-limit rejected.
`settle`	No	futures/delivery settlement; default usdt.
`symbol`	Yes	Pair or contract id.
`market_type`	No	Market venue; default spot when omitted. Allowed: spot\|futures\|delivery\|options.

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes
`items`	Yes	Public trades: time, price, amount/size; side optional (spot). create_time_ms keeps upstream units.
`limit`	Yes
`total`	Yes
`settle`	No
`symbol`	Yes	Echo input. Trade times are UTC (+00:00); convert for local display.
`cex_tool`	No	Upstream route label (omitted on open surface).
`duration_ms`	No	Server timing (omitted on open surface).
`market_type`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 9, 2026
- addedOutput schema / properties / items / items / properties / contract / description
```
Added value: +"Derivative contract identifier when applicable."
```
- addedOutput schema / properties / items / items / properties / currency_pair / description
```
Added value: +"Spot pair echo when provided (e.g. BTC_USDT)."
```

Changed4 schema fields changedSep 9, 2026

changedOutput schema / properties / items / description

Previous value: -"Public trades: time, side, price, amount/size (UTC)."New value: +"Public trades: time, price, amount/size; side optional (spot). create_time_ms keeps upstream units."

changedOutput schema / properties / items / items / properties / create_time_ms / description

Previous value: -"Trade time Unix ms (string)."New value: +"Upstream trade time field (name historical). Spot usually Unix ms; futures/delivery often Unix seconds with fraction; options may omit. Do not assume ms from the name alone."

changedOutput schema / properties / items / items / properties / create_time_ms_utc / description

Previous value: -"RFC3339 UTC (+00:00)."New value: +"RFC3339 UTC (+00:00) converted with the correct upstream unit."

changedOutput schema / properties / items / items / properties / side / description

Previous value: -"buy or sell (or upstream equivalent)."New value: +"buy/sell when provided (typically spot). Derivatives often omit side and use signed size."

Changed3 schema fields changedSep 8, 2026

changedOutput schema / properties / items / description

Previous value: -"Public trades with create_time / create_time_ms, side, price, amount (field set varies by market_type). Times UTC (+00:00)."New value: +"Public trades: time, side, price, amount/size (UTC)."

changedOutput schema / properties / items / items / additionalProperties
```
Previous value: -trueNew value: +false
```

addedOutput schema / properties / items / items / properties

Added value: +{
+  "amount": {
+    "description": "Base amount (spot).",
+    "type": "string"
+  },
+  "contract": {
+    "type": "string"
+  },
+  "create_time": {
+    "description": "Trade time Unix seconds (string).",
+    "type": "string"
+  },
+  "create_time_ms": {
+    "description": "Trade time Unix ms (string).",
+    "type": "string"
+  },
+  "create_time_ms_utc": {
+    "description": "RFC3339 UTC (+00:00).",
+    "type": "string"
+  },
+  "create_time_utc": {
+    "description": "RFC3339 UTC (+00:00).",
+    "type": "string"
+  },
+  "currency_pair": {
+    "type": "string"
+  },
+  "deal": {
+    "description": "Quote notional when provided.",
+    "type": "string"
+  },
+  "id": {
+    "description": "Trade id.",
+    "type": "string"
+  },
+  "price": {
+    "description": "Trade price.",
+    "type": "string"
+  },
+  "side": {
+    "description": "buy or sell (or upstream equivalent).",
+    "type": "string"
+  },
+  "size": {
+    "description": "Contract size when upstream uses size.",
+    "type": "string"
+  }
+}

Changed8 schema fields changedSep 8, 2026

addedInput schema / properties / limit / default
```
Added value: +50
```

changedInput schema / properties / limit / description

Previous value: -"Recent trades count; default 50, max 400. Values above max are rejected."New value: +"Recent trades count; omit for default 50; minimum 1, maximum 400. Over-limit rejected."

addedInput schema / properties / limit / maximum
```
Added value: +400
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / market_type / description

Previous value: -"spot (default)|futures|delivery|options"New value: +"Market venue; default spot when omitted. Allowed: spot|futures|delivery|options."

addedInput schema / properties / market_type / enum

Added value: +[
+  "spot",
+  "futures",
+  "delivery",
+  "options"
+]

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

addedOutput schema / properties / items / description

Added value: +"Public trades with create_time / create_time_ms, side, price, amount (field set varies by market_type). Times UTC (+00:00)."

Changed5 schema fields changedSep 8, 2026

removedInput schema / properties / extra

Removed value: -{
-  "additionalProperties": true,
-  "description": "Optional Gate API passthrough.",
-  "type": "object"
-}

changedInput schema / properties / limit / description

Previous value: -"Recent trades count; default 50, max 400."New value: +"Recent trades count; default 50, max 400. Values above max are rejected."

addedOutput schema / properties / cex_tool / description

Added value: +"Upstream route label (omitted on open surface)."

addedOutput schema / properties / duration_ms / description

Added value: +"Server timing (omitted on open surface)."

changedOutput schema / required

Previous value: -[
-  "symbol",
-  "market_type",
-  "limit",
-  "cex_tool",
-  "total",
-  "count",
-  "items",
-  "duration_ms"
-]New value: +[
+  "symbol",
+  "market_type",
+  "limit",
+  "total",
+  "count",
+  "items"
+]

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

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, open-world, and idempotent behavior; the description adds concrete caveats (no account access, no order placement, no transfers, fractional-second timestamps, signed-size semantics) that go beyond the structured data.

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?

Dense and front-loaded, but the safety message is stated twice ('Does not place orders' and 'no order placement'), adding slight redundancy.

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?

Covers the required symbol, all optional parameters with defaults and constraints, unit behavior, and the tool's safety boundaries. Enough for an agent to invoke it without further documentation.

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?

Schema covers all 4 parameters, and the description reinforces defaults, the 1–400 limit range, the over-limit rejection, and the futures-specific settle parameter. It adds create_time_ms and side semantics that are not obvious from raw field names.

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?

Opens with a specific verb and resource: 'recent Gate trade prints for a trading pair or contract.' This immediately distinguishes it from sibling chart, order-book, or account tools.

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 conveys a clear research/read-only use case and spells out what it does not do, but it never names alternatives or gives a when-to-use vs when-not-to-use rule. The intent is implied, not explicit.

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.