Skip to main content
Glama
coinpaprika

CoinPaprika MCP Server

Official

getExchanges

Retrieve a ranked list of cryptocurrency exchanges tracked by CoinPaprika, including trust score, active markets, and 24h volume. Use to find top exchanges by volume or obtain exchangeId for further queries.

Instructions

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
NameRequiredDescriptionDefault
limitNoNumber of exchanges to return (default: 50, max: 250)
quotesNoComma-separated quote currencies
Behavior5/5

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

Discloses read-only nature, no API key requirement, and parameter limits (default/max for limit, format for quotes). No annotations provided, but description fully covers behavioral traits.

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?

Compact yet complete: main purpose first, then usage guidance, then parameter details. Every sentence adds value without redundancy.

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?

Given no output schema, description explains what each exchange includes (id, name, trust score, etc.). Covers auth, read-only, and parameter constraints adequately.

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?

Adds meaning beyond schema: explains quotes as 'comma-separated list of quote currencies for the volume figures' with example 'usd,btc', and limit with default/max values.

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?

Description clearly states 'List exchanges tracked by CoinPaprika as a list ranked by rank' with specific fields, distinguishing it from siblings like getExchangeByID and getExchangeMarkets.

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?

Explicitly tells when to use this tool ('top exchanges by volume', 'biggest crypto exchanges') and names alternatives (getExchangeByID, getExchangeMarkets).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/coinpaprika/coinpaprika-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server