Cryptocompare

Price Multi

price_multi

Read-onlyIdempotent

Current crypto spot prices from CoinDesk Data (formerly CryptoCompare) for many coins at once (fsyms) quoted in many symbols (tsyms), aggregated across major exchanges. Requires your own CoinDesk Data API key.

Input Schema

TableJSON Schema

Name	Required	Description
`e`	No
`sign`	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.
`extraParams`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 3, 2026

changedInput schema / examples

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

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": {
+    "additionalProperties": {
+      "type": "number"
+    },
+    "type": "object"
+  },
+  "description": "Multi-coin price response",
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower. The description adds genuine behavioral context beyond them: the external data source (CoinDesk Data/CryptoCompare), aggregation scope, and the user-supplied API key requirement. Rate limits or quota behavior are not mentioned.

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?

Two sentences, front-loaded with the core capability and scoped to the data source. No filler; every clause carries information. Slightly dense but well-structured.

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 needn't be explained, and the data source and auth requirement are covered. However, for a 6-parameter tool with near-zero schema coverage and close siblings (price, price_full), the description leaves parameter usage and sibling selection under-specified.

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 17% (only _apiKey documented), so the description must carry the burden. It clarifies that fsyms means coins and tsyms means quote symbols, but gives no syntax guidance (comma-separated) and completely ignores the e, sign, and extraParams parameters.

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 and resource ('Current crypto spot prices... aggregated across major exchanges') plus scope ('for many coins at once... quoted in many symbols'). The 'many coins at once' phrasing implicitly contrasts with a single-coin sibling like price, but no sibling is named, so it stops short of full differentiation.

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 gives the precondition ('Requires your own CoinDesk Data API key') but offers no explicit when-to-use guidance relative to price, price_full, or histo_* siblings. The alternative routing (crypto pack, crypto-feeds) lives only in the _apiKey schema field, 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.