Crypto

Get Crypto Market

get_crypto_market

Read-onlyIdempotent

Get top cryptocurrencies ranked by market cap. Returns rank, name, symbol, USD price, market cap, 24h volume, and 24h % change for each.

Input Schema

Name	Required	Description	Default
`limit`	No	Number of coins to return (1-100, default 10)
`_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.

Output Schema

Name	Required	Description
`_note`	No	Why the fallback was used
`coins`	Yes
`currency`	Yes
`_fallback`	No	True when served from the fallback upstream

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedAug 11, 2026

addedOutput schema / description

Added value: +"Top coins by market cap. TWO PATHS, like get_crypto_price: on the coinpaprika path every figure is populated; when coinpaprika is unavailable (it returns HTTP 402 once its quota is spent) the pack falls back to a coinbase listing that carries names and symbols but NOT the market figures, so price/market_cap arrive null and _fallback is true. The numeric fields are nullable for that reason — a null here means \"this upstream did not supply it\", not zero."

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"
+}

removedOutput schema / properties / coins / items / properties / change_24h_pct / description
```
Removed value: -"24h price change percentage"
```
changedOutput schema / properties / coins / items / properties / change_24h_pct / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```
removedOutput schema / properties / coins / items / properties / id / description
```
Removed value: -"CoinGecko coin ID"
```
removedOutput schema / properties / coins / items / properties / market_cap / description
```
Removed value: -"Market capitalization"
```
changedOutput schema / properties / coins / items / properties / market_cap / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```
removedOutput schema / properties / coins / items / properties / name / description
```
Removed value: -"Cryptocurrency name"
```
removedOutput schema / properties / coins / items / properties / price / description
```
Removed value: -"Current price in quote currency"
```
changedOutput schema / properties / coins / items / properties / price / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```
removedOutput schema / properties / coins / items / properties / rank / description
```
Removed value: -"Market cap rank"
```
changedOutput schema / properties / coins / items / properties / rank / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```
removedOutput schema / properties / coins / items / properties / symbol / description
```
Removed value: -"Cryptocurrency symbol (uppercase)"
```
removedOutput schema / properties / coins / items / properties / volume_24h / description
```
Removed value: -"24h trading volume"
```
changedOutput schema / properties / coins / items / properties / volume_24h / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```

changedOutput schema / properties / coins / items / required

Previous value: -[
-  "rank",
-  "id",
-  "name",
-  "symbol",
-  "price",
-  "market_cap",
-  "volume_24h",
-  "change_24h_pct"
-]New value: +[
+  "id",
+  "name",
+  "symbol"
+]

removedOutput schema / properties / currency / description
```
Removed value: -"Quote currency (lowercase)"
```

Changed1 schema field changedJul 29, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "limit": 10
-  },
-  {
-    "limit": 50,
-    "vs_currency": "usd"
-  }
-]New value: +[
+  {
+    "limit": 10
+  },
+  {
+    "limit": 50
+  }
+]

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"
+}

Changed2 schema fields changedMay 14, 2026

changedInput schema / properties / limit / description

Previous value: -"Number of coins (1-100, default 10)"New value: +"Number of coins to return (1-100, default 10)"

removedInput schema / properties / vs_currency

Removed value: -{
-  "description": "Quote currency (default: usd)",
-  "type": "string"
-}

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "coins": {
+      "items": {
+        "properties": {
+          "change_24h_pct": {
+            "description": "24h price change percentage",
+            "type": "number"
+          },
+          "id": {
+            "description": "CoinGecko coin ID",
+            "type": "string"
+          },
+          "market_cap": {
+            "description": "Market capitalization",
+            "type": "number"
+          },
+          "name": {
+            "description": "Cryptocurrency name",
+            "type": "string"
+          },
+          "price": {
+            "description": "Current price in quote currency",
+            "type": "number"
+          },
+          "rank": {
+            "description": "Market cap rank",
+            "type": "number"
+          },
+          "symbol": {
+            "description": "Cryptocurrency symbol (uppercase)",
+            "type": "string"
+          },
+          "volume_24h": {
+            "description": "24h trading volume",
+            "type": "number"
+          }
+        },
+        "required": [
+          "rank",
+          "id",
+          "name",
+          "symbol",
+          "price",
+          "market_cap",
+          "volume_24h",
+          "change_24h_pct"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "currency": {
+      "description": "Quote currency (lowercase)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "currency",
+    "coins"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "limit": 10
+  },
+  {
+    "limit": 50,
+    "vs_currency": "usd"
+  }
+]

First observedApr 14, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the return-field list but does not reveal additional behavioral traits like rate limits, endpoint selection, or keyless vs. API-key behavior; those details appear only in the parameter schema, not the description.

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 a single, efficient sentence that front-loads the core action and result fields. It contains no filler or redundant information, every phrase earning its place.

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?

Given the low complexity, rich annotations, 100% schema coverage, and the presence of an output schema, the description is complete. It conveys the purpose, sorting basis, and returned fields, leaving no significant gaps for an agent to invoke the tool 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 100%: both 'limit' and '_apiKey' have meaningful descriptions, including default values and optionality. The main description adds no parameter-level meaning beyond what the schema already provides, so the baseline score of 3 applies.

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 states the exact operation: 'Get top cryptocurrencies ranked by market cap' and enumerates the returned fields. This clearly distinguishes it from sibling tools like get_crypto_price, get_crypto_history, and get_crypto_global by specifying the ranking scope and data fields.

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?

The description implies a use case—retrieving a market-wide ranked list—but provides no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives or exclusions, so the agent must infer appropriate usage from the tool's purpose.

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.