CoinPaprika

getExchanges

Read-onlyIdempotent

List exchanges tracked by CoinPaprika as a list ranked by rank, each with id, name, trust score, active market count and 24h volume. Use for 'top exchanges by volume', 'biggest crypto exchanges', or to find an exchangeId before calling getExchangeByID. For one exchange's full stats use getExchangeByID; for its trading pairs use getExchangeMarkets. Read-only. Params: quotes (optional, default 'usd') is a comma-separated list of quote currencies for the volume figures, for example 'usd,btc'; limit (optional, default 50, max 250) caps how many exchanges return. No API key required.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`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
`exchanges`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 2, 2026

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": {
+    "exchanges": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "active": {
+            "type": "boolean"
+          },
+          "adjusted_rank": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "api_status": {
+            "type": "boolean"
+          },
+          "currencies": {
+            "type": "number"
+          },
+          "description": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "fiats": {
+            "items": {},
+            "type": "array"
+          },
+          "id": {
+            "type": "string"
+          },
+          "last_updated": {
+            "type": "string"
+          },
+          "links": {},
+          "markets": {
+            "type": "number"
+          },
+          "markets_data_fetched": {
+            "type": "boolean"
+          },
+          "message": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "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"
+          },
+          "reported_rank": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "website_status": {
+            "type": "boolean"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "exchanges"
+  ],
+  "type": "object"
+}

First observedJul 28, 2026

TDQS

A4.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, and the description reinforces this with 'Read-only' and 'No API key required.' It also adds useful behavioral context beyond annotations: results are ranked by rank, limit can cap result count, and quotes control which volume figures are returned.

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 compact and well-structured: purpose and output fields first, then usage guidance with alternatives, then parameter semantics. Every sentence adds value and there is no redundant or filler text.

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 tool is a read-only list endpoint with an output schema available, so the description does not need to explain return values. It covers purpose, ranking, output fields, use cases, alternative tools, auth requirements, and both optional parameters, making it fully sufficient for an agent to decide when and how to call it.

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

Parameters5/5

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

The schema only describes rationale in detail, leaving limit and quotes undocumented there. The description compensates fully by explaining quotes as a comma-separated list of quote currencies with default 'usd' and an example, and limit as an optional cap with default 50 and max 250. Together with the schema's detailed rationale description, every parameter is meaningfully documented.

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 a specific verb and resource: 'List exchanges tracked by CoinPaprika as a list ranked by rank, each with id, name, trust score, active market count and 24h volume.' It clearly names the output fields and ranking order, and it distinguishes this tool from getExchangeByID and getExchangeMarkets by naming what those alternatives do.

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 states when to use this tool ('top exchanges by volume', 'biggest crypto exchanges', 'to find an exchangeId') and names the alternatives for different needs: getExchangeByID for full stats and getExchangeMarkets for trading pairs. This provides clear routing guidance with no ambiguity.

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?