Cryptocompare

Social Stats

social_stats

Read-onlyIdempotent

Fetch social media stats for a coin by CoinDesk Data (formerly CryptoCompare) coinId: Twitter followers, Reddit subscribers, Facebook likes, GitHub activity. 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": {
      "coinId": 1,
      "_apiKey": "your-cryptocompare-api-key"
    },
    "name": "social_stats"
  }
}

Input Schema

Name	Required	Description	Default
`coinId`	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
`Data`	No	Social stats data

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 3, 2026

changedInput schema / examples

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

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: -[
-  "coinId"
-]New value: +[
+  "_apiKey",
+  "coinId"
+]

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "coinId": 1
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Social media statistics for a coin",
+  "properties": {
+    "Data": {
+      "description": "Social stats data",
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds genuinely useful disclosure beyond that: the operation requires the caller's own third-party API key and the data is sourced from CoinDesk Data (formerly CryptoCompare), which explains identity and auth expectations. No rate limits or error behavior are mentioned, but that is a minor gap given annotation coverage.

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, zero filler, front-loaded with the verb and resource before the supporting detail. The return-field enumeration and the API-key prerequisite are both dense with information an agent needs.

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-value documentation is not required, yet the description still previews the metrics. For a two-parameter read tool with full annotation coverage, the remaining gaps — how to obtain a coinId, behavior on invalid ids or missing key — are small.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: _apiKey is well documented but coinId is bare. The description compensates for exactly that gap by pinning coinId to the CoinDesk Data/CryptoCompare namespace, steering the agent away from CoinGecko-style ids. It still doesn't state the id's format or where to look one up (e.g., all_coins), so compensation is partial.

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?

Specific verb ('Fetch') plus a precisely scoped resource ('social media stats for a coin'), and it enumerates the returned metrics (Twitter followers, Reddit subscribers, Facebook likes, GitHub activity). The CoinDesk Data/CryptoCompare coinId qualifier and the social-data subject cleanly separate it from price, histo_*, and news siblings.

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?

The description establishes clear context and a hard prerequisite: an agent-supplied CoinDesk Data API key, which prevents a failed attempt at a keyless call. It stops short of naming alternatives or exclusions within the description itself (the fallback to the `crypto`/`crypto-feeds` packs lives in the schema's _apiKey text).

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.