Cryptocompare

News Feeds

news_feeds

Read-onlyIdempotent

List crypto news source publishers CoinDesk Data (formerly CryptoCompare) aggregates (CoinDesk, CoinTelegraph, etc.) with feed IDs and metadata. Use as a directory before filtering news() by source. 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": "news_feeds"
  }
}

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	Default
No arguments

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": "Available news feeds",
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the read-only, safe-to-repeat nature is covered. The description adds the important context that a key is required and never supplied by the platform, complementing the schema. However, it does not describe rate limits, response shape, or feed ID format beyond high-level structure.

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 sentences front-load the purpose and follow with the routing and prerequisite. No redundancy or filler; each clause aids correct invocation.

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?

For a one-parameter, read-only directory tool with an output schema, the description is nearly complete: it covers purpose, routing, and key ownership. Output schema presence means return values need not be explained. Only minor gaps remain around feed metadata structure or pagination, if any.

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?

The schema has 100% description coverage on the single _apiKey parameter, including signup instructions and fallback packs. The description mirrors the key requirement without adding syntax or format detail beyond what the schema already provides. Baseline 3 is appropriate since the schema carries the parameter documentation.

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?

The description states a specific verb and resource ('List crypto news source publishers'), names the underlying provider, and gives concrete examples. It also distinguishes itself from sibling news() by positioning itself as a directory before filtering.

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

Usage Guidelines5/5

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

It explicitly says when to use this tool ('as a directory before filtering news() by source'), which is exactly the conditional routing an agent needs. It also names the alternative and the prerequisite for the alternative in the schema.

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.