Skip to main content
Glama

getHistoricalTickerByContract

Read-onlyIdempotent

Get a token's price and market history by its contract address, as a time series. Use for 'token price on 2024-01-01 by address', 'hourly history for a contract'. For its current price use getTickerByContract; by coin id use getTickersHistoricalById. Read-only. Params: platformId (required) chain id like 'eth-ethereum'; contractAddress (required) token address; 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). Free tier on this hosted server: daily intervals up to a year back and hourly intervals up to 24 hours back; anything else returns a structured CP402_PAID_ENDPOINT stub.

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').usd
startYesRequired. Start timestamp. Accepts ISO 8601 ('2026-01-15T00:00:00Z') or date-only ('2026-01-15'). UTC.
intervalNoOptional. Sampling interval, default '1d'. On this hosted server (free tier) daily and coarser intervals ('1d', '24h', '7d', '14d', '30d', '90d', '365d') are served for the last year and hourly ones ('1h', '2h', '3h', '6h', '12h') for the last 24 hours; minute intervals ('5m', '15m', '30m') and older ranges need a paid plan with your own key. Upstream supports additional intervals; consult CoinPaprika docs if you need something outside this list.1d
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.
platformIdYesPlatform identifier (e.g., 'eth-ethereum', 'bnb-binance-coin'). Use getPlatforms to discover valid platforms.
contractAddressYesToken contract address on the platform. EVM addresses are case-insensitive; Solana addresses are case-sensitive base58.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ticksYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / interval / default
      Previous value: -"5m"New value: +"1d"
    • changedInput schema / properties / interval / description
      Previous value: -"Optional. 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."New value: +"Optional. Sampling interval, default '1d'. On this hosted server (free tier) daily and coarser intervals ('1d', '24h', '7d', '14d', '30d', '90d', '365d') are served for the last year and hourly ones ('1h', '2h', '3h', '6h', '12h') for the last 24 hours; minute intervals ('5m', '15m', '30m') and older ranges need a paid plan with your own key. Upstream supports additional intervals; consult CoinPaprika docs if you need something outside this list."
    • changedInput schema / properties / rationale / description
      Previous value: -"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."New value: +"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."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": true,
      +  "properties": {
      +    "ticks": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "market_cap": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "price": {
      +            "type": "number"
      +          },
      +          "timestamp": {
      +            "type": "string"
      +          },
      +          "volume_24h": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "ticks"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Even though annotations already declare readOnlyHint and idempotentHint, the description adds valuable non-obvious behavior: it requires a Starter+ plan, details hosted free-tier restrictions (daily intervals up to a year, hourly intervals up to 24 hours), and states that unsupported ranges return a structured CP402_PAID_ENDPOINT stub. This goes well beyond the annotation baseline and informs the agent of real-world failure modes.

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 and front-loaded: purpose sentence, usage examples, sibling routing, param summary, and plan constraints all earn their place. It loses one point because the param summary largely duplicates schema content and contains the interval-default contradiction, preventing it from being a perfectly clean, concise definition.

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 8 parameters, full schema coverage, and an output schema, the description supplies the missing operational context: plan requirements, hosted-server interval limits, and sibling-tool routing. It is nearly complete, but the interval-default contradiction and the absence of the required rationale parameter in the narrative summary leave minor gaps that could cause an incorrect invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description does add examples for platformId and contractAddress plus plan limits. However, it directly contradicts the schema by claiming interval default '5m' while the schema declares default '1d', and it omits the required 'rationale' parameter from its param summary. The incorrect default is actively misleading for an otherwise well-documented parameter set.

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 opens with a specific verb + resource + scope: 'Get a token's price and market history by its contract address, as a time series.' It immediately distinguishes itself from siblings by explicitly naming getTickerByContract for current price and getTickersHistoricalById for coin-id lookups, so an agent can tell exactly which tool to select.

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 gives concrete query patterns ('token price on 2024-01-01 by address', 'hourly history for a contract') and explicit routing rules: use getTickerByContract for current price, getTickersHistoricalById for coin-id historical data. It also clarifies plan-tier eligibility by explaining free-tier interval limits and when a paid API key is required.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources