Cryptocompare

All Coins

all_coins

Read-onlyIdempotent

Return the full CoinDesk Data (formerly CryptoCompare) coin list with symbol, name, CoinId, algorithm, proof type, and asset type for every tracked cryptocurrency. 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": {
      "_apiKey": "your-cryptocompare-api-key"
    },
    "name": "all_coins"
  }
}

Input Schema

Name	Required	Description	Default
`_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
`Data`	No	Coin data keyed by symbol
`BaseLinkUrl`	No	Base URL for coin links
`BaseImageUrl`	No	Base URL for coin images

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 3, 2026

changedInput schema / examples

Previous value: -[
-  {}
-]New value: +[
+  {
+    "_apiKey": "your-cryptocompare-api-key"
+  }
+]

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"
+}

addedInput schema / required
```
Added value: +[
+  "_apiKey"
+]
```

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples
```
Added value: +[
+  {}
+]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Complete cryptocurrency list",
+  "properties": {
+    "BaseImageUrl": {
+      "description": "Base URL for coin images",
+      "type": "string"
+    },
+    "BaseLinkUrl": {
+      "description": "Base URL for coin links",
+      "type": "string"
+    },
+    "Data": {
+      "additionalProperties": {
+        "type": "object"
+      },
+      "description": "Coin data keyed by symbol",
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

B3.2/5.0

Behavior3/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 structurally. The description adds the meaningful prerequisite that an external API key is required, but discloses nothing about rate limits, pagination, or failure modes beyond that.

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, no wasted words, with the resource and returned fields front-loaded followed by the key requirement. Efficient and well-sized for the operation.

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?

With an output schema present, return values need no explaining, and the description still names the returned fields plus the auth prerequisite. Adequate for a simple single-parameter read tool, though it could note behavior when the key is missing.

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?

There is a single parameter and schema description coverage is 100%, so the schema already fully documents _apiKey. The description adds no syntax or format detail beyond what the schema provides, which is exactly the baseline-3 case.

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 (Return) and resource (the full CoinDesk Data / CryptoCompare coin list) and enumerates the fields returned, so it is clearly distinct from siblings like all_exchanges or price. It stops short of explicitly naming which sibling to use instead, so it does not reach a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description says the tool requires your own API key but gives no when-to-use/when-not-to-use guidance and names no alternative. The useful routing hint (use the crypto pack without a key) lives only in the schema description, not 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.