CoinPaprika

getCoinMarkets

Read-onlyIdempotent

Get the specific markets and trading pairs where a coin trades, with per-market price and 24h volume. Use for 'where can I buy X', 'X price on Binance', 'best market for X'. For just the list of exchange names use getCoinExchanges. Read-only; coinId is a canonical id, quotes sets quote currencies, limit caps results. No API key required.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`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.
`quotes`	No
`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
`markets`	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": {
+    "markets": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "adjusted_volume_24h_share": {
+            "type": "number"
+          },
+          "base_currency_id": {
+            "type": "string"
+          },
+          "base_currency_name": {
+            "type": "string"
+          },
+          "category": {
+            "type": "string"
+          },
+          "exchange_id": {
+            "type": "string"
+          },
+          "exchange_name": {
+            "type": "string"
+          },
+          "fee_type": {
+            "type": "string"
+          },
+          "last_updated": {
+            "type": "string"
+          },
+          "market_url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "outlier": {
+            "type": "boolean"
+          },
+          "pair": {
+            "type": "string"
+          },
+          "quote_currency_id": {
+            "type": "string"
+          },
+          "quote_currency_name": {
+            "type": "string"
+          },
+          "quotes": {
+            "additionalProperties": {
+              "additionalProperties": true,
+              "properties": {
+                "ath_date": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "ath_price": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "market_cap": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "market_cap_change_24h": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "percent_change_12h": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "percent_change_15m": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "percent_change_1h": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "percent_change_1y": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "percent_change_24h": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "percent_change_30d": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "percent_change_30m": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "percent_change_6h": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "percent_change_7d": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "percent_from_price_ath": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "price": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "volume_24h": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "volume_24h_change_24h": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                }
+              },
+              "type": "object"
+            },
+            "type": "object"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "markets"
+  ],
+  "type": "object"
+}

First observedJul 28, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds context beyond the annotations: 'No API key required' (auth info), and clarifies how quotes and limit behave. It does not contradict the annotations ('Read-only' aligns with readOnlyHint).

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?

Three sentences with zero waste: purpose is front-loaded, example queries follow, then the sibling alternative and parameter/behavior notes. Every clause earns its place, and the structure leads with the most decision-relevant information.

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?

With an output schema present, return values need no explanation. The description covers purpose, usage triggers, the differentiating sibling, parameter semantics, read-only behavior, and auth requirements. Nothing an agent needs to call this tool correctly is missing.

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 description coverage is 50% — coinId and rationale are richly documented in the schema, but limit and quotes have only bare type/default entries. The description compensates by explaining 'quotes sets quote currencies, limit caps results' and the canonical-id nature of coinId, which are the exact under-documented aspects.

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 a specific verb and resource ('Get the specific markets and trading pairs where a coin trades') and adds concrete query examples ('where can I buy X', 'X price on Binance') that make the tool's purpose unmistakable. It also names the sibling it is not ('For just the list of exchange names use getCoinExchanges'), so an agent can differentiate it from the closest alternative.

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?

The description explicitly gives usage triggers ('Use for ...'), which tells the agent exactly when to invoke this tool. It also names the alternative tool and the condition that selects it ('For just the list of exchange names use getCoinExchanges'), leaving nothing to inference.

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?