Cryptocompare

Price Full

price_full

Read-onlyIdempotent

Fetch full market snapshot for multiple crypto pairs (fsyms → tsyms): price, 24h change/%, volume, market cap, open/high/low from CoinDesk Data (formerly CryptoCompare). 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": {
      "fsyms": "BTC",
      "tsyms": "USD",
      "_apiKey": "your-cryptocompare-api-key"
    },
    "name": "price_full"
  }
}

Input Schema

Name	Required	Description
`e`	No
`fsyms`	Yes
`tsyms`	Yes
`_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.

Output Schema

Name	Required	Description	Default
`RAW`	No	Raw price data
`DISPLAY`	No	Formatted display data

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 3, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "fsyms": "BTC",
-    "tsyms": "USD"
-  },
-  {
-    "fsyms": "BTC,ETH",
-    "tsyms": "USD,EUR"
-  }
-]New value: +[
+  {
+    "_apiKey": "your-cryptocompare-api-key",
+    "fsyms": "BTC",
+    "tsyms": "USD"
+  },
+  {
+    "_apiKey": "your-cryptocompare-api-key",
+    "fsyms": "BTC,ETH",
+    "tsyms": "USD,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: -[
-  "fsyms",
-  "tsyms"
-]New value: +[
+  "_apiKey",
+  "fsyms",
+  "tsyms"
+]

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "fsyms": "BTC",
+    "tsyms": "USD"
+  },
+  {
+    "fsyms": "BTC,ETH",
+    "tsyms": "USD,EUR"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Full price snapshot with RAW and DISPLAY data",
+  "properties": {
+    "DISPLAY": {
+      "description": "Formatted display data",
+      "type": "object"
+    },
+    "RAW": {
+      "description": "Raw price data",
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: the upstream data source (CoinDesk Data, formerly CryptoCompare) and the hard requirement that the caller supply their own API key. It does not mention rate limits or quota behavior tied to the key.

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 tight sentences: the snapshot scope and field list come first, the data-source and API-key constraint second. No filler, no restating of the title or annotations.

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 values need not be described, and the description covers the key operational prerequisite (own API key) plus the data source. The only gap is the unexplained `e` parameter, which is missing from both schema and description.

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 25%, so the description must carry weight; it does explain the fsyms → tsyms direction (from-symbols to target symbols), which is a real gain over the bare schema. However, the `e` parameter is undocumented in both schema and description, leaving one of four parameters unexplained.

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?

The description names a specific verb ('Fetch'), a specific resource ('full market snapshot for multiple crypto pairs'), and enumerates the returned fields (price, 24h change/%, volume, market cap, open/high/low). It clearly conveys scope via 'multiple pairs', which separates it from single-pair siblings like price. It stops short of explicitly naming price_multi or top_volume_full, so an agent must infer the boundary.

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?

'Multiple crypto pairs' and 'full snapshot' imply batch/multi-field usage versus leaner siblings, but no explicit when-to-use or when-not-to-use guidance is given. The API-key prerequisite and the fallback to the `crypto` pack appear only in the schema's _apiKey description, not in the tool description itself.

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.