CoinPaprika

getContracts

Read-onlyIdempotent

List the token contract addresses tracked on one platform as a list, mapping each contract to its CoinPaprika coin id. Use for 'contracts on ethereum', 'what tokens does BSC have', or to map a contract address to a coin id. Find the platformId first with getPlatforms; for one contract's live price use getTickerByContract, and for its history use getHistoricalTickerByContract. Read-only. Params: platformId (required) is a platform id such as 'eth-ethereum' or 'bsc-binance-smart-chain'; limit (optional, default 50, max 250) caps how many contracts return. An unknown platformId returns an error. No API key required.

Input Schema

TableJSON Schema

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

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint; description adds that it's read-only, requires no API key, and returns an error for unknown platformId. Adds context beyond annotations, though could mention pagination or result ordering.

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?

Four sentences, front-loaded with purpose, then usage guidance, then parameter details. No wasted words.

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?

Given no output schema, description mentions mapping contract to coin id but does not specify return format (e.g., array of objects). Covers error behavior and required inputs well. Completeness is good but not perfect due to missing return structure.

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 low (33%); description compensates by explaining platformId as a platform id like 'eth-ethereum' and limit with default/max values. Adds meaning beyond schema for both documented parameters, but rationale is already in schema.

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 verb and resource: 'List the token contract addresses... mapping each contract to its CoinPaprika coin id.' Provides concrete use cases and distinguishes from related tools like getTickerByContract and getHistoricalTickerByContract.

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 the tool ('contracts on ethereum', 'what tokens does BSC have') and when not to (for single contract price/history, use other tools). Also instructs to find platformId first with getPlatforms.

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

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

Need Help?