CoinPaprika

getCoinOHLCVToday

Read-onlyIdempotent

Get today's in-progress OHLC candle for a coin. Use for 'today's high and low for ETH'. For the current spot price use getTickersById; for yesterday's full candle use getCoinOHLCVLatest, and for older prices getTickersHistoricalById. Read-only; coinId is a canonical id (resolve with resolveId). No API key required.

Input Schema

TableJSON 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

TableJSON Schema

Name	Required	Description	Default
`ohlcv`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description still adds useful behavior: the candle is 'in-progress' (i.e., partial/updating data), no API key is required, and coinId must be a canonical id resolved via resolveId. No rate-limit or refresh cadence info, so not a full 5.

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?

Purpose is front-loaded, followed by usage, alternatives, and behavioral notes in four tight sentences. Every sentence carries distinct, actionable information with no redundancy.

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

Completeness5/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 not be explained. The description covers purpose, the in-progress caveat, sibling routing, id resolution, and auth requirements — everything an agent needs to call it correctly.

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 67%, and the coinId schema already exhaustively documents the canonical slug format, examples, and the resolveId prerequisite. The description only echoes that guidance and says nothing about the quote or rationale parameters, so it adds little beyond structured data. Baseline 3 fits.

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 today's in-progress OHLC candle for a coin'), with the key qualifier that the candle is in-progress/partial. It explicitly distinguishes itself from getCoinOHLCVLatest, getTickersById, and getTickersHistoricalById, so an agent can route correctly without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use case ('today's high and low for ETH') plus named alternatives for adjacent needs: getTickersById for spot price, getCoinOHLCVLatest for yesterday's candle, getTickersHistoricalById for older prices. This is textbook when/when-not/alternatives guidance.

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?