Skip to main content
Glama
Sign In
Bitcompare MCP Server

Bitcompare MCP Server

Official
by bitcompare
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Historical coin price chart

coin_history
Read-onlyIdempotent

Fetch historical price timeseries for a coin over the nearest supported window (1, 7, 30, 90, or 365 days; default 7). Use it to analyze past price trends.

Instructions

Historical price timeseries for a coin. Requests use the nearest 1, 7, 30, 90 or 365-day window (default 7), bounded by available data. Requires a paid plan (Starter or above) over MCP; this endpoint does not apply the rate-history per-plan day clamp.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "coinId": "<coinId>"
    },
    "name": "coin_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoRequested days, rounded to the nearest supported window: 1, 7, 30, 90 or 365 days (default 7). Requests above 365 use 365; available data may be shorter.
coinIdYesCanonical coin id (e.g. "bitcoin")

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.2.0
    • addedInput schema / properties / coinId
      Added value: +{
+  "description": "Canonical coin id (e.g. \"bitcoin\")",
+  "type": "string"
+}
    • changedInput schema / properties / days / description
      Previous value: -"Days of history"New value: +"Requested days, rounded to the nearest supported window: 1, 7, 30, 90 or 365 days (default 7). Requests above 365 use 365; available data may be shorter."
    • removedInput schema / properties / symbol
      Removed value: -{
-  "description": "Coin symbol (e.g. \"btc\")",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "symbol"
-]New value: +[
+  "coinId"
+]
    • addedOutput schema / properties / data
      Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "coinId": {
+      "type": "string"
+    },
+    "days": {
+      "type": "integer"
+    },
+    "lastUpdated": {
+      "description": "ISO-8601 timestamp of the most recent refresh",
+      "type": "string"
+    },
+    "prices": {
+      "description": "Price points, oldest → newest",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "marketCap": {
+            "type": "number"
+          },
+          "price": {
+            "type": "number"
+          },
+          "timestamp": {
+            "description": "Unix epoch milliseconds",
+            "type": "number"
+          },
+          "volume": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "timestamp",
+          "price"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "source": {
+      "description": "Where the data came from",
+      "enum": [
+        "rate_history",
+        "cache",
+        "coingecko"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "coinId",
+    "days",
+    "source",
+    "prices",
+    "lastUpdated"
+  ],
+  "type": "object"
+}
    • removedOutput schema / properties / points
      Removed value: -{
-  "description": "Price points, oldest → newest",
-  "items": {
-    "additionalProperties": true,
-    "properties": {
-      "timestamp": {
-        "description": "ISO-8601 timestamp of the data point",
-        "type": "string"
-      },
-      "value": {
-        "description": "The recorded numeric value",
-        "type": "number"
-      }
-    },
-    "required": [
-      "timestamp",
-      "value"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}
    • removedOutput schema / properties / symbol
      Removed value: -{
-  "type": "string"
-}
    • changedOutput schema / required
      Previous value: -[
-  "symbol",
-  "points"
-]New value: +[
+  "data"
+]
  2. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), the description discloses two non-obvious behaviors: requests snap to the nearest supported window and are bounded by available data, and the endpoint requires a paid plan (Starter+) over MCP. That plan gate is exactly the kind of context annotations cannot convey. It stops short of 5 because it doesn't describe the failure mode when the plan is insufficient.

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, front-loaded with the purpose, then the windowing rule, then the plan constraint. No filler, and each clause carries distinct information an agent needs before calling.

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?

For a two-parameter read-only tool with a full output schema and complete parameter coverage, this covers purpose, windowing behavior, and the plan requirement. The only real gap is the absence of sibling routing guidance, which is relevant given many adjacent price/rate tools.

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 100%, and the schema already documents the rounding-to-nearest-window behavior and the 7-day default, so the description mostly restates it. It adds only the assurance that the same windowing applies endpoint-side; no new meaning for coinId. Baseline 3 is appropriate when the schema does the heavy lifting.

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 combination: 'Historical price timeseries for a coin.' An agent can tell this is a price-history endpoint rather than a current-price or rate endpoint. It never names a sibling to route away from, so it stops short of a 5.

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?

Usage is only implied by the noun phrase 'historical price timeseries' and by the aside contrasting this endpoint with the 'rate-history per-plan day clamp', which hints at get_rate_history without saying to use that tool instead. There is no explicit when-to-use/when-not statement or prerequisite flow for choosing among get_price, get_rate_history, etc.

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

Deploy Server

Other Tools