Cryptocompare

Histo Hour

histo_hour

Read-onlyIdempotent

Hourly historical OHLC + volume for a crypto pair (BTC/USD, ETH/USDT, etc.). Use for medium-timeframe crypto charting, swing-trading analysis, multi-day backtests. Requires your own CoinDesk Data API key.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fsym": "BTC",
      "tsym": "USD",
      "limit": 24,
      "_apiKey": "your-cryptocompare-api-key"
    },
    "name": "histo_hour"
  }
}

Input 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

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": 24,
-    "tsym": "USD"
-  },
-  {
-    "fsym": "ETH",
-    "limit": 168,
-    "tsym": "USD"
-  }
-]New value: +[
+  {
+    "_apiKey": "your-cryptocompare-api-key",
+    "fsym": "BTC",
+    "limit": 24,
+    "tsym": "USD"
+  },
+  {
+    "_apiKey": "your-cryptocompare-api-key",
+    "fsym": "ETH",
+    "limit": 168,
+    "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": 24,
+    "tsym": "USD"
+  },
+  {
+    "fsym": "ETH",
+    "limit": 168,
+    "tsym": "USD"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Hourly 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 readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context by disclosing the external authentication requirement (own CoinDesk Data API key) and the shape of the returned data (OHLC + volume). It doesn't mention rate limits or how `limit`/`aggregate` affect the result.

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?

Two dense sentences and a prerequisite clause with zero filler; the what-it-returns statement comes first and the usage contexts follow, so the most important information is front-loaded.

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-value details are unnecessary, and the auth requirement is covered. However, with 7 parameters at 14% schema coverage, the definition is not complete enough for an agent to confidently use the timeframe (`toTs`), exchange (`e`) or aggregation controls.

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% across 7 parameters, so the description must carry the load, but it only conveys the pair format ('BTC/USD, ETH/USDT') implicitly tied to fsym/tsym. The `e`, `toTs`, `limit` and `aggregate` parameters are undocumented in both places, leaving an agent with little guidance on anything beyond the base pair.

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 (returns), resource (historical OHLC + volume) and granularity (hourly) for a crypto pair, which cleanly separates it from the sibling histo_day and histo_minute tools without needing to open 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete usage contexts ('medium-timeframe crypto charting, swing-trading analysis, multi-day backtests') and states the prerequisite of a personal CoinDesk Data API key. It stops short of naming an explicit alternative or when-not condition in the description text, though the _apiKey schema field does route users to the `crypto` pack.

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.