Cryptocompare

Top Market Cap

top_market_cap

Read-onlyIdempotent

Return the top cryptocurrencies ranked by market capitalization denominated in a quote symbol (tsym); paginates with page parameter. Requires your own CoinDesk Data API key.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No
`tsym`	No
`limit`	No
`_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

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: -[
-  {
-    "limit": 30,
-    "tsym": "USD"
-  },
-  {
-    "limit": 100
-  }
-]New value: +[
+  {
+    "_apiKey": "your-cryptocompare-api-key",
+    "limit": 30,
+    "tsym": "USD"
+  },
+  {
+    "_apiKey": "your-cryptocompare-api-key",
+    "limit": 100
+  }
+]

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: +[
+  {
+    "limit": 30,
+    "tsym": "USD"
+  },
+  {
+    "limit": 100
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Top coins by market capitalization",
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4/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. The description adds two useful behavioral facts beyond them: pagination via the page parameter and the external-auth requirement (own API key). Return format is left to the output schema.

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, front-loaded with purpose and scope, followed by the pagination and auth notes. No filler or repetition of the title.

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 not be described, and the annotations cover the safety profile. Purpose, pagination, and auth are all covered; the only gap is the undocumented 'limit' parameter, which is minor for a top-N listing tool.

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 coverage is only 25%, so the description must carry more weight. It clarifies tsym (quote symbol) and page (pagination), adding meaning beyond the bare schema, but leaves 'limit' entirely unexplained in both schema and description.

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?

States a specific verb ('Return') and resource ('top cryptocurrencies ranked by market capitalization'), plus the denomination dimension (quote symbol tsym). The market-cap ranking criterion inherently distinguishes it from volume- or pairs-based siblings like top_volume_full and top_pairs.

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?

Provides a prerequisite ('Requires your own CoinDesk Data API key') but gives no explicit when-to-use vs when-to-use-an-alternative guidance. The alternative routing (crypto pack, crypto-feeds) lives only in the schema's _apiKey description, not here, so usage is only implied.

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.