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

TableJSON 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

TableJSON 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.

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.5/5.0

Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is established. The description adds genuine behavioral context beyond that: 'at the current rate' clarifies this is a spot conversion (not historical), and 'No API key required' discloses authentication requirements. The 'Read-only' phrasing repeats an annotation, so not full credit, but the additional traits earn a strong score.

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, each earning its place: core function with examples, sibling routing, and a compact summary of parameter roles plus auth requirements. No filler, no repetition of schema details beyond a brief clarifying clause.

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 description covers purpose, usage conditions, sibling differentiation, auth requirements, and parameter semantics, while the 100%-coverage schema handles detailed parameter constraints (including the 0-value warning on amount) and the output schema handles return-value expectations. Error behavior for invalid symbols is also covered in the schema ('symbols like BTC are rejected upstream'). Nothing essential is missing for correct invocation.

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%, so the parameters are already fully documented in the schema (slugs, required status, default amount, rationale rules). The description's note that 'baseCurrencyId and quoteCurrencyId are canonical ids and amount is the quantity to convert' is a light restatement that reinforces but does not materially extend the schema. Baseline 3 is appropriate.

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: 'Convert an amount from one crypto or fiat to another at the current rate,' and grounds it with concrete examples ('how much is 0.5 BTC in USD'). It explicitly differentiates from the sibling getTickersById, which handles the no-amount case, so an agent can distinguish it without opening the 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?

The description provides explicit routing: 'For a plain coin price without an amount, use getTickersById.' This names the alternative and the condition that selects it, and the example phrasings clarify the intended call patterns. No ambiguity is left about when this tool is the right choice.

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?