Skip to main content
Glama

Cryptocompare

by io.github.pipeworx-io

News

news
Read-onlyIdempotent

CoinDesk Data (formerly CryptoCompare) aggregated crypto news feed: Bitcoin/Ethereum/altcoin headlines, exchange announcements, regulatory updates, market analysis. Filter by category (BTC, ETH, Trading, Regulation) or feed. Use for "what is happening in crypto right now". Prefer over web search for crypto-specific news.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lTsNo
langNo
feedsNo
sortOrderNo
categoriesNo
excludeCategoriesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
DataNoArray of news articles

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "lang": "EN",
+    "sortOrder": "latest"
+  },
+  {
+    "categories": "blockchain",
+    "feeds": "cointelegraph"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "News articles feed",
+  "properties": {
+    "Data": {
+      "description": "Array of news articles",
+      "items": {
+        "properties": {
+          "categories": {
+            "description": "Article categories",
+            "type": "string"
+          },
+          "guid": {
+            "description": "Article GUID",
+            "type": "string"
+          },
+          "id": {
+            "description": "Article ID",
+            "type": "string"
+          },
+          "imageurl": {
+            "description": "Article image URL",
+            "type": "string"
+          },
+          "lang": {
+            "description": "Language code",
+            "type": "string"
+          },
+          "published_on": {
+            "description": "Publication timestamp",
+            "type": "number"
+          },
+          "source": {
+            "description": "News source",
+            "type": "string"
+          },
+          "title": {
+            "description": "Article title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Article URL",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already define readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds that it's aggregated from CoinDesk Data (formerly CryptoCompare) and mentions filtering by category/feed, but does not disclose additional behavior such as rate limits, pagination, or return format details. It adds some context but not deeper behavioral insights.

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?

The description is only two sentences, front-loaded with the core purpose and supported by usage guidance. Every sentence contributes value: the first defines the feed and its content, the second explains filtering and when to use it. No filler or redundant information.

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?

Given the tool has an output schema and strong annotations, the description is reasonably complete. It provides purpose, usage guidance, and some parameter context. However, it omits details on all parameters and doesn't mention return format or any special behavior, though output schema likely covers that. Overall, it's adequate for an agent to understand the tool's role.

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

Parameters2/5

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

Input schema has 6 parameters with 0% description coverage, so the description must compensate. It explains the 'categories' and 'feeds' parameters by listing examples (BTC, ETH, Trading, Regulation) and mentioning filtering, but leaves other parameters (lTs, lang, sortOrder, excludeCategories) undocumented. The description partially covers the parameter semantics but is insufficient for the full set.

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 clearly states it's an 'aggregated crypto news feed' with specific content types (Bitcoin/Ethereum/altcoin headlines, exchange announcements, regulatory updates, market analysis). It mentions filtering by category or feed, and explicitly positions it for 'what is happening in crypto right now', distinguishing it from web search as a specialized source.

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 provides clear usage context: 'Use for "what is happening in crypto right now"' and 'Prefer over web search for crypto-specific news.' However, it doesn't explicitly exclude alternatives like news_categories or news_feeds, which are siblings and could be used for discovering filter options, nor does it mention when not to use this tool for non-news queries.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation3/5

Several tool families overlap heavily: ask_pipeworx, its beta, and grounded variants, the six polymarket_* tools, and the three price endpoints (price, price_full, price_multi) can be confused despite distinct purposes. Long descriptions provide some disambiguation, but an agent must read carefully to select the correct tool.

Naming Consistency4/5

Tool names mostly follow snake_case with verb_noun or noun_noun patterns (all_coins, compare_entities, top_market_cap), and related families share clear prefixes (histo_*, polymarket_*). Minor deviations exist (bare verbs like remember/forget, brand names like ask_pipeworx), but the overall pattern is readable and consistent.

Tool Count2/5

With 46 tools, the server is far beyond the 3-15 well-scoped range and nearly double the 25-tool threshold for 'too many'. Many tools are unrelated to the server's apparent crypto purpose (generate_llms_txt, scan_dependency, memory helpers), making it feel like a general-purpose utility rather than a focused data service.

Completeness3/5

The crypto data surface is fairly complete (spot, historical, top lists, news, social stats, exchange metadata), and the Pipeworx meta-tools (ask_pipeworx, deep_research, entity_profile) cover a broad range of factual queries. However, there are notable gaps: no direct way to fetch pipeworx:// citation URIs, and no advanced crypto order-book/trade endpoints, leaving some workflows as dead ends.

Resources