Cryptocompare

Histo Day

histo_day

Read-onlyIdempotent

Daily historical OHLC + volume for a crypto pair (BTC/USD, ETH/USDT, etc.). Use for long-horizon crypto charting, multi-year backtests, and macro 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": 365,
-    "tsym": "USD"
-  },
-  {
-    "fsym": "ETH",
-    "limit": 90,
-    "tsym": "EUR"
-  }
-]New value: +[
+  {
+    "_apiKey": "your-cryptocompare-api-key",
+    "fsym": "BTC",
+    "limit": 365,
+    "tsym": "USD"
+  },
+  {
+    "_apiKey": "your-cryptocompare-api-key",
+    "fsym": "ETH",
+    "limit": 90,
+    "tsym": "EUR"
+  }
+]

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": 365,
+    "tsym": "USD"
+  },
+  {
+    "fsym": "ETH",
+    "limit": 90,
+    "tsym": "EUR"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Daily 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

A4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds a genuinely load-bearing behavioral constraint — the requirement to supply your own CoinDesk Data API key — which is not visible in 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?

Three tight sentences: what it returns, when to use it, and the auth prerequisite. The core capability is front-loaded with zero 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?

An output schema exists, so return-shape explanation is unnecessary, and the auth requirement plus intended use are covered. The remaining gap is the undocumented optional parameters (toTs, aggregate, e), which an agent cannot infer.

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 only 14% (1 of 7 params documented), so the description needs to compensate, and it only partly does. It clarifies the fsym/tsym pair convention via 'BTC/USD, ETH/USDT' examples but says nothing about limit, toTs, aggregate, or e.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource with granularity: 'Daily historical OHLC + volume for a crypto pair.' The word 'Daily' implicitly separates it from histo_hour/histo_minute, but the description never names those siblings, so the differentiation is left to inference.

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?

Gives concrete use cases ('long-horizon crypto charting, multi-year backtests, macro analysis') that clarify the fitting context, and the schema note points at fallbacks when no key exists. It stops short of explicitly stating when to prefer histo_hour or histo_minute instead.

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.