Skip to main content
Glama

Cryptocompare

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Price

price
Read-onlyIdempotent

Current crypto spot price from CoinDesk Data (formerly CryptoCompare): one coin (fsym) quoted in many fiat or crypto symbols (tsyms), aggregated across major exchanges. Requires your own CoinDesk Data API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eNo
fsymYes
signNo
tsymsYes
_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.
extraParamsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "fsym": "BTC",
-    "tsyms": "USD,EUR"
-  },
-  {
-    "e": "Kraken",
-    "fsym": "ETH",
-    "tsyms": "USD"
-  }
-]New value: +[
+  {
+    "_apiKey": "your-cryptocompare-api-key",
+    "fsym": "BTC",
+    "tsyms": "USD,EUR"
+  },
+  {
+    "_apiKey": "your-cryptocompare-api-key",
+    "e": "Kraken",
+    "fsym": "ETH",
+    "tsyms": "USD"
+  }
+]
    • 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",
-  "tsyms"
-]New value: +[
+  "_apiKey",
+  "fsym",
+  "tsyms"
+]
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "fsym": "BTC",
+    "tsyms": "USD,EUR"
+  },
+  {
+    "e": "Kraken",
+    "fsym": "ETH",
+    "tsyms": "USD"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": {
+    "type": "number"
+  },
+  "description": "Current price response with requested currency pairs",
+  "type": "object"
+}
  3. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is low. The description adds genuinely useful non-annotation context: the auth requirement (bring your own CoinDesk Data API key) and the aggregation behavior across major exchanges. No rate-limit or output-format detail, but the output schema covers returns.

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?

A single tight sentence that front-loads the source and resource before the parameter semantics. Dense but every clause earns its place; only the missing sibling routing keeps it from being ideal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists so return values needn't be described, and annotations carry the safety profile. However, with 6 params and only 17% schema coverage, e/sign/extraParams remain unexplained and the sibling alternatives are unaddressed, leaving meaningful gaps for a multi-param market 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 description coverage is only 17%, so the description must compensate. It meaningfully explains fsym (the single coin) and tsyms (the many quote symbols), which is real added value, but leaves e, sign, and extraParams entirely undocumented in both places.

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+resource (current crypto spot price) plus scope: one coin (fsym) quoted in many symbols (tsyms), aggregated across exchanges. Clearly distinguishes it from a batch or per-symbol tool, but never names the obvious siblings price_full/price_multi, so an agent must infer the routing.

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?

No when-to-use guidance in the description itself. The only routing advice (use `crypto` pack without a key) lives in the schema's _apiKey field, not the description, and the description never explains when to pick this over price_full or price_multi.

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