Crypto

Get Crypto Price

get_crypto_price

Read-onlyIdempotent

REAL-TIME spot price for any cryptocurrency. PREFER OVER WEB SEARCH for "what is BTC trading at", "price of ETH", "BNB price", current market cap, 24h move. Returns price USD, market cap, 24h % change — refreshed every few seconds upstream. Accepts common names ("bitcoin", "ethereum", "solana", "binance coin"), tickers ("BTC", "ETH", "SOL", "BNB", "XRP", "ADA", "DOGE"), or coinpaprika IDs ("btc-bitcoin"). Powered by coinpaprika with automatic failover to Coinbase/CryptoCompare if it is rate-limited, so it always returns a real price.

Input Schema

Name	Required	Description	Default
`_apiKey`	No	Optional — your own CoinPaprika Pro API key for a dedicated quota (uses the api-pro endpoint). Omit to use the keyless free endpoint; get_crypto_price additionally fails over to Coinbase/CryptoCompare if coinpaprika is throttled.
`coin_id`	Yes	Coin name, ticker, or coinpaprika ID (e.g., "bitcoin", "BTC", "btc-bitcoin")

Output Schema

Name	Required	Description
`id`	Yes
`name`	No	Coinpaprika path only
`rank`	No	Market-cap rank; coinpaprika path only
`_note`	No	Why the fallback was used
`source`	No	Which upstream answered
`symbol`	Yes
`_fallback`	No	True when served from the fallback upstream
`price_usd`	Yes
`low_24h_usd`	No	Not returned by the current coinpaprika response; kept for back-compat
`high_24h_usd`	No	Not returned by the current coinpaprika response; kept for back-compat
`last_updated`	No	Upstream quote timestamp (ISO-8601); coinpaprika path only
`change_24h_pct`	No	Coinpaprika path only
`market_cap_usd`	No	Coinpaprika path only
`volume_24h_usd`	No	Coinpaprika path only

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedAug 9, 2026

changedOutput schema / description

Previous value: -"Current price for a coin. Falls back to a coinbase spot price when coinpaprika is unavailable; on that path only id/symbol/price_usd/source are present and _fallback is true, so the richer market fields are optional by design."New value: +"Current price for a coin. Two shapes: the coinpaprika path carries name/rank/market-cap/volume/24h-change/last_updated; when coinpaprika is unavailable (it returns HTTP 402 when its quota is spent) the pack falls back to a coinbase spot price carrying only id/symbol/price_usd/source plus _fallback and _note. Only the three fields common to BOTH paths are required."

changedOutput schema / properties / high_24h_usd / description

Previous value: -"Coinpaprika path only"New value: +"Not returned by the current coinpaprika response; kept for back-compat"

addedOutput schema / properties / last_updated

Added value: +{
+  "description": "Upstream quote timestamp (ISO-8601); coinpaprika path only",
+  "type": "string"
+}

changedOutput schema / properties / low_24h_usd / description

Previous value: -"Coinpaprika path only"New value: +"Not returned by the current coinpaprika response; kept for back-compat"

addedOutput schema / properties / rank

Added value: +{
+  "description": "Market-cap rank; coinpaprika path only",
+  "type": [
+    "number",
+    "null"
+  ]
+}

Changed20 schema fields changedAug 8, 2026

addedOutput schema / description

Added value: +"Current price for a coin. Falls back to a coinbase spot price when coinpaprika is unavailable; on that path only id/symbol/price_usd/source are present and _fallback is true, so the richer market fields are optional by design."

addedOutput schema / properties / _fallback

Added value: +{
+  "description": "True when served from the fallback upstream",
+  "type": "boolean"
+}

addedOutput schema / properties / _note

Added value: +{
+  "description": "Why the fallback was used",
+  "type": "string"
+}

changedOutput schema / properties / change_24h_pct / description

Previous value: -"24h price change percentage"New value: +"Coinpaprika path only"

changedOutput schema / properties / change_24h_pct / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

changedOutput schema / properties / high_24h_usd / description

Previous value: -"24h high price in USD"New value: +"Coinpaprika path only"

changedOutput schema / properties / high_24h_usd / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

removedOutput schema / properties / id / description
```
Removed value: -"CoinGecko coin ID"
```

changedOutput schema / properties / low_24h_usd / description

Previous value: -"24h low price in USD"New value: +"Coinpaprika path only"

changedOutput schema / properties / low_24h_usd / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

changedOutput schema / properties / market_cap_usd / description

Previous value: -"Market capitalization in USD"New value: +"Coinpaprika path only"

changedOutput schema / properties / market_cap_usd / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

changedOutput schema / properties / name / description

Previous value: -"Cryptocurrency name"New value: +"Coinpaprika path only"

removedOutput schema / properties / price_usd / description
```
Removed value: -"Current price in USD"
```

changedOutput schema / properties / price_usd / type

Previous value: -"number"New value: +[
+  "number",
+  "string"
+]

addedOutput schema / properties / source

Added value: +{
+  "description": "Which upstream answered",
+  "type": "string"
+}

removedOutput schema / properties / symbol / description
```
Removed value: -"Cryptocurrency symbol (uppercase)"
```

changedOutput schema / properties / volume_24h_usd / description

Previous value: -"24h trading volume in USD"New value: +"Coinpaprika path only"

changedOutput schema / properties / volume_24h_usd / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

changedOutput schema / required

Previous value: -[
-  "id",
-  "name",
-  "symbol",
-  "price_usd",
-  "market_cap_usd",
-  "volume_24h_usd",
-  "change_24h_pct",
-  "high_24h_usd",
-  "low_24h_usd"
-]New value: +[
+  "id",
+  "symbol",
+  "price_usd"
+]

Changed1 schema field changedJun 17, 2026

addedInput schema / properties / _apiKey

Added value: +{
+  "description": "Optional — your own CoinPaprika Pro API key for a dedicated quota (uses the api-pro endpoint). Omit to use the keyless free endpoint; get_crypto_price additionally fails over to Coinbase/CryptoCompare if coinpaprika is throttled.",
+  "type": "string"
+}

Changed1 schema field changedMay 14, 2026

changedInput schema / properties / coin_id / description

Previous value: -"CoinGecko coin ID (e.g., bitcoin, ethereum, solana)"New value: +"Coin name, ticker, or coinpaprika ID (e.g., \"bitcoin\", \"BTC\", \"btc-bitcoin\")"

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "change_24h_pct": {
+      "description": "24h price change percentage",
+      "type": "number"
+    },
+    "high_24h_usd": {
+      "description": "24h high price in USD",
+      "type": "number"
+    },
+    "id": {
+      "description": "CoinGecko coin ID",
+      "type": "string"
+    },
+    "low_24h_usd": {
+      "description": "24h low price in USD",
+      "type": "number"
+    },
+    "market_cap_usd": {
+      "description": "Market capitalization in USD",
+      "type": "number"
+    },
+    "name": {
+      "description": "Cryptocurrency name",
+      "type": "string"
+    },
+    "price_usd": {
+      "description": "Current price in USD",
+      "type": "number"
+    },
+    "symbol": {
+      "description": "Cryptocurrency symbol (uppercase)",
+      "type": "string"
+    },
+    "volume_24h_usd": {
+      "description": "24h trading volume in USD",
+      "type": "number"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "symbol",
+    "price_usd",
+    "market_cap_usd",
+    "volume_24h_usd",
+    "change_24h_pct",
+    "high_24h_usd",
+    "low_24h_usd"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "coin_id": "bitcoin"
+  },
+  {
+    "coin_id": "ethereum"
+  }
+]

First observedApr 14, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint and other annotations, the description discloses that data refreshes every few seconds and includes automatic failover to Coinbase/CryptoCompare if coinpaprika is rate-limited, ensuring a real price is always returned. This is valuable behavioral context not present in annotations.

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 one well-organized paragraph, front-loaded with the core purpose and followed by specific usage examples and technical details. Every sentence contributes unique information; there is no redundancy or filler.

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?

The description covers the tool's purpose, input flexibility, API key option, fallback behavior, and return fields. Combined with the rich annotations and output schema, it provides a complete picture for an agent to select and invoke the tool correctly.

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

Parameters4/5

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

Schema coverage is 100% with descriptions for both parameters. The description adds extra semantics by explicitly listing accepted input forms (common names, tickers, coinpaprika IDs) and explaining the optional _apiKey behavior, which goes beyond the basic schema and justifies a score above the baseline.

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 opens with 'REAL-TIME spot price for any cryptocurrency', which is a specific verb + resource that clearly states the tool's function. It also differentiates from web search and implies distinction from sibling crypto tools like get_crypto_history by focusing on spot price.

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?

It explicitly advises 'PREFER OVER WEB SEARCH for...' and lists concrete query examples, giving strong when-to-use guidance. It doesn't explicitly mention sibling tools like get_crypto_market or get_crypto_history as alternatives for related but different needs, so it stops short of full when-not-to-use coverage.

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

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