CoinPaprika

getExchangeByID

Read-onlyIdempotent

Get details for a specific exchange: 24h volume, market count, trust score, links and fiat support. Use for 'tell me about Binance', 'Coinbase exchange stats', 'is X a trustworthy exchange'. For the pairs traded there use getExchangeMarkets; find the exchange id first with search or getExchanges. Read-only; exchangeId is an exchange id such as binance. No API key required.

Input Schema

TableJSON Schema

Name	Required	Description
`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.
`exchangeId`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`name`	No
`fiats`	No
`links`	No
`active`	No
`quotes`	No
`markets`	No
`message`	No
`api_status`	No
`currencies`	No
`description`	No
`last_updated`	No
`adjusted_rank`	No
`reported_rank`	No
`website_status`	No
`markets_data_fetched`	No

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

First observedJul 28, 2026

TDQS

A4.4/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 useful behavioral context beyond the annotations by stating 'No API key required' and clarifying that exchangeId is a friendly id 'such as binance'. This is not a contradiction, and the added access and id-format details improve transparency.

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 first, then usage examples, then disambiguation, then access and id guidance. Every sentence earns its place, and the most important scoping information is front-loaded. There is no filler or redundant restatement of the tool name.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only get-by-id tool, the description covers the core workflow, examples, id discovery, and authentication requirements. The output schema exists, so return-value details do not need to be enumerated. The only notable gap is the undocumented optional quotes parameter, but the overall definition is still sufficient for correct selection and invocation in most cases.

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?

The description adds real meaning for exchangeId by clarifying it is an exchange id such as 'binance' and explaining how to obtain it. The required rationale parameter is documented in the schema with examples. However, schema description coverage is only 33% overall, and the optional quotes parameter is not explained anywhere, leaving one parameter without semantic guidance.

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 clearly states the action: 'Get details for a specific exchange' and enumerates the specific fields returned (24h volume, market count, trust score, links, fiat support). It also provides concrete example user queries, which helps an agent recognize when this tool applies. It is well differentiated from the sibling getExchangeMarkets by explicitly scoping this tool to exchange details rather than traded pairs.

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 gives explicit when-to-use guidance with example phrases like 'tell me about Binance' and 'is X a trustworthy exchange'. It also names the alternative tool for a different need: 'For the pairs traded there use getExchangeMarkets'. It further instructs the agent to find the exchange id first via search or getExchanges, leaving no ambiguity about the intended workflow.

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?