Cryptocompare

Histo Minute

histo_minute

Read-onlyIdempotent

Minute-granularity historical OHLC + volume for a crypto pair (BTC/USD, ETH/USDT, etc.) across major exchanges. Use for short-timeframe charting, intraday backtests, and tick-level analysis. Requires your own CoinDesk Data API key.

Input Schema

TableJSON Schema

Name	Required	Description
`e`	No
`fsym`	Yes
`toTs`	No
`tsym`	Yes
`limit`	No
`_apiKey`	Yes	Your own CoinDesk Data (formerly CryptoCompare) API key — required, Pipeworx does not supply one for this pack. Free signup: https://developers.coindesk.com/. Without a key, use the `crypto` pack (get_crypto_price) for prices/daily history or `crypto-feeds` for news instead.
`aggregate`	No

Output Schema

TableJSON Schema

Name	Required	Description
`Data`	No	Array of OHLC candles
`Type`	No	Data type
`TimeTo`	No	End timestamp of data
`Response`	No	Response status
`TimeFrom`	No	Start timestamp of data
`Aggregated`	No	Whether data is aggregated

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 3, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "fsym": "BTC",
-    "limit": 60,
-    "tsym": "USD"
-  },
-  {
-    "aggregate": 5,
-    "fsym": "ETH",
-    "limit": 30,
-    "tsym": "USD"
-  }
-]New value: +[
+  {
+    "_apiKey": "your-cryptocompare-api-key",
+    "fsym": "BTC",
+    "limit": 60,
+    "tsym": "USD"
+  },
+  {
+    "_apiKey": "your-cryptocompare-api-key",
+    "aggregate": 5,
+    "fsym": "ETH",
+    "limit": 30,
+    "tsym": "USD"
+  }
+]

addedInput schema / properties / _apiKey

Added value: +{
+  "description": "Your own CoinDesk Data (formerly CryptoCompare) API key — required, Pipeworx does not supply one for this pack. Free signup: https://developers.coindesk.com/. Without a key, use the `crypto` pack (get_crypto_price) for prices/daily history or `crypto-feeds` for news instead.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "fsym",
-  "tsym"
-]New value: +[
+  "_apiKey",
+  "fsym",
+  "tsym"
+]

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "fsym": "BTC",
+    "limit": 60,
+    "tsym": "USD"
+  },
+  {
+    "aggregate": 5,
+    "fsym": "ETH",
+    "limit": 30,
+    "tsym": "USD"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Minute OHLC candlestick data",
+  "properties": {
+    "Aggregated": {
+      "description": "Whether data is aggregated",
+      "type": "boolean"
+    },
+    "Data": {
+      "description": "Array of OHLC candles",
+      "items": {
+        "properties": {
+          "close": {
+            "description": "Closing price",
+            "type": "number"
+          },
+          "high": {
+            "description": "Highest price",
+            "type": "number"
+          },
+          "low": {
+            "description": "Lowest price",
+            "type": "number"
+          },
+          "open": {
+            "description": "Opening price",
+            "type": "number"
+          },
+          "time": {
+            "description": "Unix timestamp",
+            "type": "number"
+          },
+          "volumefrom": {
+            "description": "Volume in base coin",
+            "type": "number"
+          },
+          "volumeto": {
+            "description": "Volume in target coin",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "Response": {
+      "description": "Response status",
+      "type": "string"
+    },
+    "TimeFrom": {
+      "description": "Start timestamp of data",
+      "type": "number"
+    },
+    "TimeTo": {
+      "description": "End timestamp of data",
+      "type": "number"
+    },
+    "Type": {
+      "description": "Data type",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld, so the safety profile is covered. The description adds genuinely useful context (own API key required, coverage across major exchanges), but says nothing about rate limits, response shape, or pagination behavior for large limit values.

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?

Three tight sentences, front-loading granularity and resource before use cases and the auth requirement. No filler, though the use-case sentence could carry an alternative-tool pointer to earn its space more fully.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no prose, and the auth prerequisite is stated. However, with 7 parameters at 14% coverage, the description leaves meaningful gaps around limit, aggregate, and time-range semantics that an agent would need to call the tool confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 14% (just _apiKey), and 7 parameters exist. The description indirectly clarifies fsym/tsym ('crypto pair (BTC/USD, ETH/USDT)') and e ('across major exchanges'), but says nothing about limit, toTs, or aggregate, leaving most parameters undocumented in both schema and text.

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?

States a specific verb and resource ('historical OHLC + volume') with exact granularity ('Minute-granularity') and scope ('across major exchanges', 'crypto pair'). The minute granularity cleanly distinguishes it from the histo_day and histo_hour siblings without the agent needing to open a schema.

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?

Names concrete use cases ('short-timeframe charting, intraday backtests, and tick-level analysis') and states a prerequisite ('Requires your own CoinDesk Data API key'). It does not explicitly say when to prefer histo_hour/histo_day, but the granularity framing implicitly routes the choice.

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

All Cryptocompare 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.