CoinPaprika

priceConverter

Read-onlyIdempotent

Convert an amount from one crypto or fiat to another at the current rate, e.g. 'how much is 0.5 BTC in USD', 'convert 100 USDC to EUR'. For a plain coin price without an amount, use getTickersById. Read-only; baseCurrencyId and quoteCurrencyId are canonical ids and amount is the quantity to convert. No API key required.

Input Schema

Name	Required	Description
`amount`	No	Optional. Amount of base currency to convert (default 1). Passing 0 returns a 0-valued response, which is rarely what you want; use 1 to get a unit-rate quote.
`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.
`baseCurrencyId`	Yes	Required. Source CoinPaprika coin slug (e.g., 'btc-bitcoin'). Full slugs only; symbols like 'BTC' are rejected upstream.
`quoteCurrencyId`	Yes	Required. Target CoinPaprika coin slug (e.g., 'usd-us-dollars', 'eth-ethereum').

Output Schema

Name	Required	Description	Default
`price`	No
`amount`	No
`base_currency_id`	No
`quote_currency_id`	No
`base_currency_name`	No
`quote_currency_name`	No
`base_price_last_updated`	No
`quote_price_last_updated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 23, 2026

changedOutput schema / properties / amount / type

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

changedOutput schema / properties / base_currency_id / type

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

changedOutput schema / properties / base_currency_name / type

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

changedOutput schema / properties / base_price_last_updated / type

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

changedOutput schema / properties / price / type

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

changedOutput schema / properties / quote_currency_id / type

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

changedOutput schema / properties / quote_currency_name / type

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

changedOutput schema / properties / quote_price_last_updated / type

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

Changed3 schema fields changedSep 2, 2026

changedInput schema / properties / amount / description

Previous value: -"Optional. Amount of base currency to convert (default 1). Passing 0 returns a 0-valued response, which is rarely what you want — use 1 to get a unit-rate quote."New value: +"Optional. Amount of base currency to convert (default 1). Passing 0 returns a 0-valued response, which is rarely what you want; use 1 to get a unit-rate quote."

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": {
+    "amount": {
+      "type": "number"
+    },
+    "base_currency_id": {
+      "type": "string"
+    },
+    "base_currency_name": {
+      "type": "string"
+    },
+    "base_price_last_updated": {
+      "type": "string"
+    },
+    "price": {
+      "type": "number"
+    },
+    "quote_currency_id": {
+      "type": "string"
+    },
+    "quote_currency_name": {
+      "type": "string"
+    },
+    "quote_price_last_updated": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedJul 28, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so 'Read-only' is largely redundant. The description does add non-annotation context: 'at the current rate' (spot vs historical) and 'No API key required', which is genuine auth/setup information. It stops short of describing rate staleness or upstream error behavior, but with annotations covering the safety profile that is a minor gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the verb and worked examples, then routing guidance, then parameter clarifications, then auth note. Dense and mostly waste-free, though the final sentence mixes param semantics and auth info in a slightly list-like way.

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?

Output schema exists so return values need no explanation, annotations cover the safety profile, and schema coverage is complete. The description supplies routing, examples, currency-id semantics and auth expectations — nothing an agent needs to call this 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 100%, so the baseline is 3. The description still adds a compact semantic gloss — baseCurrencyId/quoteCurrencyId are 'canonical ids' and amount is 'the quantity to convert' — which reinforces the slug-vs-symbol trap the schema also warns about, slightly beating 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?

States a specific verb and resource ('Convert an amount ... at the current rate') plus two concrete example queries, and explicitly contrasts with getTickersById for the plain-price case. An agent can distinguish it from siblings like getTickersById or getTickers without opening any schema.

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?

Names the alternative (getTickersById) and the exact condition that should route the agent there: 'For a plain coin price without an amount'. It also implies the counterpart case (amount present → use this tool) via the examples.

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?