Skip to main content
Glama

CoinPaprika

by com.coinpaprika.mcp

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
NameRequiredDescriptionDefault
limitNo
quotesNo
rationaleYesREQUIRED. 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.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds 'Read-only', 'No API key required', and details parameter behaviors (defaults, max values). No contradictions.

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?

Reasonably concise and front-loaded with purpose. Slightly dense but clear. Could benefit from breaking into bullet points for better scanability.

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?

Cover input parameters well and output fields. Given no output schema, description provides enough context. Complexity is moderate.

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 coverage is 33% (only rationale described). Description compensates by explaining quotes (comma-separated, default 'usd') and limit (default 50, max 250). Could mention rationale meta-parameter.

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?

Clearly states it lists exchanges ranked by rank with specific fields (id, name, trust score, active market count, 24h volume). Distinguishes 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 gives use cases: 'top exchanges by volume', 'biggest crypto exchanges', or to find exchangeId. Provides alternatives: use getExchangeByID for full stats, getExchangeMarkets for trading pairs.

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

All CoinPaprika toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have distinct purposes (e.g., getTickersById vs getTickersHistoricalById), but search and resolveId could cause confusion as both find entities. Overall, overlaps are minimal and well-documented.

Naming Consistency4/5

Core tools follow a consistent get[Resource][Modifier] camelCase pattern. Some utility tools (priceConverter, resolveId, search, keyInfo, submitFeedback, status) break the pattern, but they are clearly separate and the naming is still readable.

Tool Count3/5

With 31 tools, the server is comprehensive but slightly heavy. Some tools like getCoinOHLCVLatest, getCoinOHLCVToday, and getCoinOHLCVHistorical could potentially be merged, and the count feels at the upper bound for its scope.

Completeness4/5

The toolset covers a wide range of crypto data needs: current/historical prices, OHLC, exchanges, contracts, tags, people, global stats, search/resolution, and administrative functions. Only advanced features like news or portfolio tracking are missing.

Resources