Skip to main content
Glama
Sign In

Cryptocompare

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Top Pairs

top_pairs
Read-onlyIdempotent

Return the top trading pairs for a base coin (fsym) by 24h volume on CoinDesk Data (formerly CryptoCompare), with exchange and volume data for each pair. 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": {
      "fsym": "BTC",
      "limit": 10,
      "_apiKey": "your-cryptocompare-api-key"
    },
    "name": "top_pairs"
  }
}

Input Schema

NameRequiredDescriptionDefault
fsymYes
limitNo
_apiKeyYesYour 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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "fsym": "BTC",
-    "limit": 10
-  },
-  {
-    "fsym": "ETH"
-  }
-]New value: +[
+  {
+    "_apiKey": "your-cryptocompare-api-key",
+    "fsym": "BTC",
+    "limit": 10
+  },
+  {
+    "_apiKey": "your-cryptocompare-api-key",
+    "fsym": "ETH"
+  }
+]
    • 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: -[
-  "fsym"
-]New value: +[
+  "_apiKey",
+  "fsym"
+]
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "fsym": "BTC",
+    "limit": 10
+  },
+  {
+    "fsym": "ETH"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Top trading pairs for a coin",
+  "type": "object"
+}
  3. First observed

TDQS

A3.5/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. The description adds the meaningful operational fact that the caller must supply their own CoinDesk Data API key, but stops short of disclosing rate limits, pagination, or result caveats.

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 tightly written sentences, front-loaded with the core purpose and followed by the data-source/auth detail. No filler, though the source parenthetical '(formerly CryptoCompare)' is somewhat tangential to 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?

An output schema exists, so explaining return values is unnecessary, and the description covers the source and auth requirement. It is nearly complete for a read-only lookup, with only the 'limit' parameter and any pagination behavior left unaddressed.

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 description coverage is only 33%, with 'limit' and 'fsym' undocumented in the schema. The description clarifies 'fsym' as the base coin but says nothing about what 'limit' controls or how it bounds the pair list, so it only partially compensates for the coverage gap.

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?

The description states a clear verb and resource ('Return the top trading pairs for a base coin (fsym) by 24h volume'), plus the source and returned data ('exchange and volume data for each pair'). It is precise about scope, but never names the sibling tools it sits beside (top_volume_full, top_market_cap, price) to distinguish itself.

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 implies its use case via the volume-based ranking of trading pairs, and notes the API-key prerequisite. However, it gives no explicit when-to-use or when-not-to-use guidance relative to the many sibling tools, leaving routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Cryptocompare toolsInspect
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.

Resources