CoinPaprika

getCoinOHLCVLatest

Read-onlyIdempotent

Get the latest full-day OHLC candle (open, high, low, close and volume) for a coin. Use for 'yesterday's candle for BTC'. For the live spot price use getTickersById. Read-only; coinId must be a canonical id (resolve a bare symbol with resolveId first), quote defaults to usd. No API key required.

Input Schema

Name	Required	Description	Default
`quote`	No		usd
`coinId`	Yes	Canonical CoinPaprika coin slug in 'symbol-name' format, e.g. 'btc-bitcoin', 'eth-ethereum', 'ada-cardano'. Do NOT pass ticker symbols ('BTC', 'AAVE') or guess the slug; it is not derivable from the symbol (e.g. AAVE resolves to 'aave-new', which you could not guess). Call search or resolveId first to resolve a symbol or name to its canonical id.
`rationale`	Yes	REQUIRED. In 1-2 sentences explain WHY you are calling this tool and what you intend to do with the result. Examples: 'User asked for BTC price; calling getTickersById to fetch current USD value.' 'Building a portfolio dashboard; need OHLCV for ETH last 7 days.' This is logged and reviewed to improve the MCP. Do not include user PII or secrets; use generic descriptions.

Output Schema

Name	Required	Description	Default
`ohlcv`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 23, 2026

removedOutput schema / properties / ohlcv / items / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties / ohlcv / items / anyOf

Added value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "close": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "high": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "low": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "market_cap": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "open": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "time_close": {
+        "description": "ISO 8601 bucket close. Often '23:59:59Z' for daily candles, inclusive.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "time_open": {
+        "description": "ISO 8601 bucket open.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "volume": {
+        "type": [
+          "number",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / ohlcv / items / properties

Removed value: -{
-  "close": {
-    "type": "number"
-  },
-  "high": {
-    "type": "number"
-  },
-  "low": {
-    "type": "number"
-  },
-  "market_cap": {
-    "type": [
-      "number",
-      "null"
-    ]
-  },
-  "open": {
-    "type": "number"
-  },
-  "time_close": {
-    "description": "ISO 8601 bucket close. Often '23:59:59Z' for daily candles, inclusive.",
-    "type": "string"
-  },
-  "time_open": {
-    "description": "ISO 8601 bucket open.",
-    "type": "string"
-  },
-  "volume": {
-    "type": [
-      "number",
-      "null"
-    ]
-  }
-}

removedOutput schema / properties / ohlcv / items / type
```
Removed value: -"object"
```

Changed3 schema fields changedSep 2, 2026

changedInput schema / properties / coinId / description

Previous value: -"Canonical CoinPaprika coin slug in 'symbol-name' format, e.g. 'btc-bitcoin', 'eth-ethereum', 'ada-cardano'. Do NOT pass ticker symbols ('BTC', 'AAVE') or guess the slug — it is not derivable from the symbol (e.g. AAVE resolves to 'aave-new', which you could not guess). Call search or resolveId first to resolve a symbol or name to its canonical id."New value: +"Canonical CoinPaprika coin slug in 'symbol-name' format, e.g. 'btc-bitcoin', 'eth-ethereum', 'ada-cardano'. Do NOT pass ticker symbols ('BTC', 'AAVE') or guess the slug; it is not derivable from the symbol (e.g. AAVE resolves to 'aave-new', which you could not guess). Call search or resolveId first to resolve a symbol or name to its canonical id."

changedInput schema / properties / rationale / description

Previous value: -"REQUIRED. In 1-2 sentences explain WHY you are calling this tool and what you intend to do with the result. Examples: 'User asked for BTC price; calling getTickersById to fetch current USD value.' 'Building a portfolio dashboard; need OHLCV for ETH last 7 days.' This is logged and reviewed to improve the MCP. Do not include user PII or secrets — use generic descriptions."New value: +"REQUIRED. In 1-2 sentences explain WHY you are calling this tool and what you intend to do with the result. Examples: 'User asked for BTC price; calling getTickersById to fetch current USD value.' 'Building a portfolio dashboard; need OHLCV for ETH last 7 days.' This is logged and reviewed to improve the MCP. Do not include user PII or secrets; use generic descriptions."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "ohlcv": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "close": {
+            "type": "number"
+          },
+          "high": {
+            "type": "number"
+          },
+          "low": {
+            "type": "number"
+          },
+          "market_cap": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "open": {
+            "type": "number"
+          },
+          "time_close": {
+            "description": "ISO 8601 bucket close. Often '23:59:59Z' for daily candles, inclusive.",
+            "type": "string"
+          },
+          "time_open": {
+            "description": "ISO 8601 bucket open.",
+            "type": "string"
+          },
+          "volume": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "ohlcv"
+  ],
+  "type": "object"
+}

First observedJul 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world, so the description correctly spends its words adding context rather than repeating them: no API key required, quote defaults to usd, and coinId must be canonical. It does not mention rate limits, which day boundary the 'full day' uses, or the data source, but the output schema already covers return shape.

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?

Four short sentences with the core operation first, then the disambiguating example, then the alternative tool, then the preconditions. No sentence is filler and nothing important is buried.

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 return values need no explanation, and the description covers prerequisites, defaults, and auth status. For a simple read tool this is nearly complete; only the candle's time boundary and sibling contrast with getCoinOHLCVToday are 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 coverage is 67%, so the baseline is 3. The coinId guidance ('must be a canonical id, resolve a bare symbol with resolveId first') largely restates the already-detailed schema description, and 'quote defaults to usd' only repeats the schema default without adding accepted-value guidance for the one param the schema leaves undocumented.

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 and resource ('Get the latest full-day OHLC candle') and enumerates the returned fields (open, high, low, close, volume). It is distinguishable from the near-twin getCoinOHLCVToday by the 'full-day' qualifier and from getTickersById by the explicit pointer to it.

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?

Gives a concrete usage example ('yesterday's candle for BTC'), names the alternative for live spot price (getTickersById), and states the prerequisite resolveId step for bare symbols. It does not contrast with getCoinOHLCVToday or the historical OHLCV siblings, which is the only remaining routing gap.

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

All CoinPaprika 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.

Resources

Need Help?