Crypto Bot Audit + Market Data (x402 paid)

Gate recent trades

market_gate_trades

Read-onlyIdempotent

Gate's public fill feed for one pair: side, price, base amount, millisecond timestamp and trade id. Costs $0.001 USDC per call. Byte-identical to GET /market/gate-trades?pair=BTC_USDT&limit=20.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`pair`	Yes	Gate currency_pair, BASE_QUOTE [required]
`limit`	No	trades (max 100) (default 25)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ts`	No
`note`	No
`count`	No
`found`	No
`stale`	No
`caveat`	No
`reason`	No
`source`	No
`trades`	No
`currency_pair`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "caveat": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "count": {
+      "type": "integer"
+    },
+    "currency_pair": {
+      "type": "string"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "trades": {
+      "items": {},
+      "type": "array"
+    },
+    "ts": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only and idempotent behavior. The description adds the significant $0.001 USDC per-call cost and the byte-identical REST endpoint equivalence. This is useful behavioral context beyond the annotations, though it does not discuss rate limits or failure behavior.

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?

Three compact sentences: the first states purpose and returned fields, the second surfaces the cost, and the third gives endpoint equivalence. Every sentence earns its place and the most decision-relevant information is front-loaded.

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?

For a simple two-parameter market feed with an output schema and readOnly/idempotent annotations, the description covers purpose, output contents, cost, and endpoint behavior. Nothing essential to correctly invoking the tool is missing.

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%, with both pair and limit documented in the input schema. The description's example URL reinforces the BASE_QUOTE format and limit=20, but does not add new parameter semantics beyond what the schema already states.

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 resource (Gate's public fill feed), scopes it to one trading pair, and enumerates the returned fields (side, price, base amount, millisecond timestamp, trade id). This distinguishes it from sibling market_gate_candles, market_gate_depth, and market_gate_ticker without needing to inspect their schemas.

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 clearly implies trade-level market data use, but it does not explicitly state when to choose this tool over the sibling Gate market tools or mention exclusions. The public feed wording provides context, yet an agent is left to infer alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crypto Bot Audit + Market Data (x402 paid) 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.

Resources

Need Help?