Skip to main content
Glama
Sign In

CoinPaprika

by com.coinpaprika.mcp
OverviewDiscussionsAdmin

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

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

NameRequiredDescriptionDefault
ticksYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / ticks / items / additionalProperties
      Removed value: -true
    • addedOutput schema / properties / ticks / items / anyOf
      Added value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "market_cap": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "price": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "timestamp": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "volume_24h": {
+        "type": [
+          "number",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / ticks / items / properties
      Removed value: -{
-  "market_cap": {
-    "type": [
-      "number",
-      "null"
-    ]
-  },
-  "price": {
-    "type": "number"
-  },
-  "timestamp": {
-    "type": "string"
-  },
-  "volume_24h": {
-    "type": [
-      "number",
-      "null"
-    ]
-  }
-}
    • removedOutput schema / properties / ticks / items / type
      Removed value: -"object"
  2. 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"
+}
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly/idempotent/non-destructive), and the description adds non-obvious behavior the annotations cannot express: it needs a Starter+ plan with COINPAPRIKA_API_KEY, the hosted free tier only serves daily-over-a-year and hourly-over-24h, and out-of-tier requests return a structured CP402_PAID_ENDPOINT stub rather than a normal error. That last detail materially changes how an agent should interpret a response.

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?

Front-loaded with purpose and routing before the parameter recap, and every sentence is informational rather than filler. The plan-tier sentence is dense but necessary; trimming it would cost behaviorally important detail.

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?

For an 8-param tool with full schema coverage, annotations, and an output schema, the description supplies the missing operational context (plan gating, tier limits, stub fallback). The gaps are the stale interval default and the unmentioned required rationale parameter, both of which affect correct invocation.

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 description coverage is 100% and the schema already documents formats, defaults, and limits, so the schema carries the load; the description mostly restates it. It does add the useful 'limit caps points' framing, but it states interval defaults to '5m' while the schema declares default '1d', and it omits the required rationale parameter entirely — both can mislead an agent filling the call.

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?

States a specific verb+resource ('Get a token's price and market history by its contract address, as a time series') and immediately distinguishes itself from both siblings that serve similar data (getTickerByContract for current price, getTickersHistoricalById for coin-id lookups). An agent can route correctly without opening any schema.

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?

Gives concrete invocation examples ('token price on 2024-01-01 by address', 'hourly history for a contract') plus explicit alternatives and the condition that selects each: current price -> getTickerByContract, coin id -> getTickersHistoricalById. It also states plan eligibility and what the free tier will and will not serve.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources