Crypto Bot Audit + Market Data (x402 paid)

Kraken OHLC candles

market_kraken_ohlc

Read-onlyIdempotent

OHLCV candles for one Kraken pair: open, high, low, close, volume and trade count per bucket, oldest first. Only the intervals the venue actually serves are offered. Costs $0.001 USDC per call. Byte-identical to GET /market/kraken-ohlc?pair=XBTUSD&interval=15&limit=20.

Input Schema

TableJSON Schema

Name	Required	Description
`pair`	Yes	Kraken pair as the venue spells it: XBTUSD, ETHUSD, SOLUSD [required]
`limit`	No	how many candles (max 720) (default 48)
`interval`	No	candle width in minutes (360 is rejected by Kraken; 30 and 720 are unmeasured and therefore not offered) (default "15")

Output Schema

TableJSON Schema

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

AddedSep 24, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, lowering the bar. The description adds genuinely new behavioral facts: a $0.001 USDC cost per call, byte-identical response to a specific GET endpoint, venue-served interval restrictions, and oldest-first ordering. There is no contradiction with the 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?

The description is three sentences with the core output front-loaded, followed by interval constraints, cost, and endpoint equivalence. Every sentence earns its place, and there is no filler or redundant restatement of schema fields.

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?

With an output schema present and parameters fully described, the description covers the remaining operational essentials: interval availability, per-call cost, response ordering, and exact endpoint equivalence. No critical missing context remains for a read-only market-data tool.

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 pair spelling, limit max/default, and interval constraints. The description adds output-ordering context but does not materially improve parameter understanding beyond what the schema already provides, so the baseline of 3 applies.

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: OHLCV candles for one Kraken pair, specifying the exact fields (open, high, low, close, volume, trade count) and the oldest-first ordering. The 'Kraken' qualifier plus 'candles' distinguishes it from sibling Kraken tools such as market_kraken_depth, market_kraken_trades, and market_kraken_ticker.

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 implies the tool is for Kraken OHLCV data and notes interval restrictions, but it does not explicitly state when to prefer this over alternative market-data or candle tools. With many sibling candle tools across exchanges, explicit routing guidance would be more helpful.

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?