CoinPaprika

getCoinEvents

Read-onlyIdempotent

Get the timeline of events for a coin (launches, partnerships, hard forks, conference talks) with dates and descriptions. Use for 'what is happening with X', 'upcoming events for Ethereum', 'X roadmap events'. For prices use getTickersById. Read-only; coinId is a canonical id, limit caps results. No API key required.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`coinId`	Yes	Canonical CoinPaprika coin slug in 'symbol-name' format, e.g. 'btc-bitcoin', 'eth-ethereum', 'ada-cardano'. Do NOT pass ticker symbols ('BTC', 'AAVE') or guess the slug — it is not derivable from the symbol (e.g. AAVE resolves to 'aave-new', which you could not guess). Call search or resolveId first to resolve a symbol or name to its canonical id.
`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.

TDQS

A4.4/5.0

Behavior4/5

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

The description adds context beyond annotations by stating the tool is read-only, that coinId is a canonical id, that limit caps results, and that no API key is required. These details complement the readOnlyHint and destructiveHint annotations without contradiction. Only minor gap: no mention of pagination or rate limits, but sufficient for selection.

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?

The description is two sentences with no wasted words. It front-loads the primary purpose, then efficiently provides usage examples, alternative tool, and key behavioral notes. Every sentence serves a distinct purpose.

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?

The description covers purpose, usage context, alternatives, and key constraints (read-only, coinId format, limit behavior) with no output schema. It is complete enough for an agent to select this tool appropriately, though additional detail on output structure could improve completeness slightly.

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 coverage is 67% with detailed descriptions for coinId and rationale. The description adds minimal value for parameters beyond what the schema provides, only noting that limit caps results. For the limit parameter, the schema only has a default while the description adds the capping behavior, which helps but is not comprehensive.

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 clearly states the tool retrieves a timeline of events for a coin (launches, partnerships, hard forks, conference talks) with dates and descriptions, and distinguishes it from getTickersById for prices. This provides a specific verb and resource, clearly differentiating from sibling tools.

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 explicitly states when to use this tool ('what is happening with X', 'upcoming events for Ethereum', 'X roadmap events') and provides an alternative tool for prices ('For prices use getTickersById'), offering clear guidance on appropriate usage.

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?