Skip to main content
Glama

CoinPaprika

by com.coinpaprika.mcp

getTickersHistoricalById

Read-onlyIdempotent

Get a coin's price, market cap and volume at past times as point-in-time snapshots (not OHLC candles). Use for 'price of BTC last Tuesday', 'ETH market cap on 2024-01-01'. For OHLC chart candles use getCoinOHLCVHistorical; for the current price use getTickersById. Read-only. Params: coinId (required) canonical id like 'btc-bitcoin' (resolve via resolveId); start (required) and end (optional, default now) accept 'yyyy-mm-dd' or ISO 8601; interval (optional, default '5m'); quote (optional, default 'usd'); limit (optional, default 50, max 250) caps points. Requires a Starter+ plan (COINPAPRIKA_API_KEY).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoOptional end timestamp. Same formats as start. Defaults to now if omitted.
limitNoOptional. Number of data points (default 50, max 250).
quoteNoOptional quote currency code (default 'usd'). Examples: 'usd', 'btc', 'eth'.usd
startYesRequired. Start timestamp. Accepts ISO 8601 ('2026-01-15T00:00:00Z') or date-only ('2026-01-15'). UTC.
coinIdYesCanonical 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.
intervalNoOptional. Sampling interval. Common values: '5m', '15m', '30m', '1h', '6h', '12h', '24h', '7d', '14d', '30d'. Upstream supports additional intervals; consult CoinPaprika docs if you need something outside this list.5m
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.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds 'Read-only' and important context like requiring a Starter+ plan and explaining parameter behavior (e.g., default intervals, max limit). 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?

The description is well-structured: purpose first, usage guidance, then parameter summary. It is moderately concise without extraneous text. Every sentence provides value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While the description covers purpose, usage, and parameters, it lacks detail on output format (e.g., returned fields) and pagination behavior beyond the limit parameter. Since no output schema exists, the agent would benefit from knowing response structure.

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?

Schema description coverage is 100%, but the description adds significant value beyond schema: explains coinId format and warns against guessing slugs, details start/end formats, lists common intervals, and specifies limit defaults/max. The only missing param (rationale) is fully described 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?

The description clearly states the tool retrieves point-in-time snapshots of price, market cap, and volume for a coin at past times. It distinguishes from sibling tools getCoinOHLCVHistorical and getTickersById by explicitly stating what it is not (OHLC candles) and when to use alternatives.

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?

Provides explicit usage examples ('price of BTC last Tuesday', 'ETH market cap on 2024-01-01') and clear when-not-to-use guidelines: 'For OHLC chart candles use getCoinOHLCVHistorical; for the current price use getTickersById.' This eliminates ambiguity.

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