Crypto Bot Audit + Market Data (x402 paid)

KuCoin OHLC candles

market_kucoin_candles

Read-onlyIdempotent

KuCoin candles with base and quote (transaction-value) volume per bucket, oldest first, across every type value the venue answered. Costs $0.001 USDC per call. Byte-identical to GET /market/kucoin-candles?symbol=BTC-USDT&type=1min&limit=20.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	No	KuCoin candle type (default "1min")
`limit`	No	candles (max 1500; KuCoin answers at most 1500 per call) (default 48)
`symbol`	Yes	KuCoin symbol, BASE-QUOTE in upper case (BTC-USDT, SOL-USDT) [required]

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ts`	No
`note`	No
`rows`	No
`type`	No
`count`	No
`found`	No
`stale`	No
`caveat`	No
`reason`	No
`source`	No
`symbol`	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"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "rows": {
+      "items": {},
+      "type": "array"
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "symbol": {
+      "type": "string"
+    },
+    "ts": {
+      "type": "string"
+    },
+    "type": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds valuable behavioral context beyond that: a per-call cost of $0.001 USDC, exact byte-identical equivalence to a specific GET endpoint, and ordering/volume semantics. No contradiction with annotations.

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 concise sentences, each earning its place: the first states the resource and key data traits, the second discloses cost, and the third gives an exact endpoint equivalence. Information is front-loaded and there is no filler.

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?

With a rich output schema and annotations covering read-only/idempotent behavior, the description is largely complete. It adds cost, ordering, volume details, and endpoint equivalence. The phrase 'across every type value the venue answered' is slightly ambiguous, but not enough to prevent correct 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%, so the schema already documents symbol, type, and limit. The description adds output-level semantics like base/quote volume and oldest-first ordering, but it does not add much parameter-specific meaning beyond what the schema provides.

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 identifies the resource as KuCoin OHLC candles and specifies distinctive output traits: base and quote volume per bucket, oldest-first ordering, and coverage of every type value the venue answered. This distinguishes it from sibling candle tools such as market_okx_candles or market_gate_candles.

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 gives clear context for when to use the tool: when KuCoin candle data is needed. It does not explicitly name alternatives or exclusions, but the venue-specific wording and the byte-identical endpoint reference make the intended use unambiguous.

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?