CoinPaprika

getTickerByContract

Read-onlyIdempotent

Get the current price and market data of a token by its contract address (for on-chain and DeFi tokens). Use when you have a contract address (0x...) rather than a name. For history use getHistoricalTickerByContract. Read-only; platformId is the chain (e.g. eth-ethereum) and contractAddress the token address. No API key required.

Input Schema

TableJSON Schema

Name	Required	Description
`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
`contractAddress`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No
`name`	No
`rank`	No
`quotes`	No	Keyed by quote currency code (e.g. 'USD', 'BTC').
`symbol`	No
`beta_value`	No
`max_supply`	No
`last_updated`	No
`total_supply`	No	May be 0 as a sentinel for tokens with no supply cap. Cross-reference with CoinPaprika docs for sentinel semantics.
`first_data_at`	No
`circulating_supply`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 2, 2026

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": {
+    "beta_value": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "circulating_supply": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "first_data_at": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "last_updated": {
+      "type": "string"
+    },
+    "max_supply": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "name": {
+      "type": "string"
+    },
+    "quotes": {
+      "additionalProperties": {
+        "additionalProperties": true,
+        "properties": {
+          "ath_date": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "ath_price": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "market_cap": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "market_cap_change_24h": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "percent_change_12h": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "percent_change_15m": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "percent_change_1h": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "percent_change_1y": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "percent_change_24h": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "percent_change_30d": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "percent_change_30m": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "percent_change_6h": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "percent_change_7d": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "percent_from_price_ath": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "price": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "volume_24h": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "volume_24h_change_24h": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "description": "Keyed by quote currency code (e.g. 'USD', 'BTC').",
+      "type": "object"
+    },
+    "rank": {
+      "type": "number"
+    },
+    "symbol": {
+      "type": "string"
+    },
+    "total_supply": {
+      "description": "May be 0 as a sentinel for tokens with no supply cap. Cross-reference with CoinPaprika docs for sentinel semantics.",
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedJul 28, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds useful behavioral context by noting no API key is required and clarifying this is for current data rather than history.

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 compact and front-loaded with the core purpose, followed by usage guidance, parameter hints, and auth requirements. Every sentence adds actionable value with no redundancy.

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

Completeness5/5

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

For a simple read-only tool with an output schema present, the description covers purpose, usage conditions, alternative routing, key parameter semantics, and auth. Nothing essential is missing for an agent to invoke it correctly.

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 description coverage is only 33%, and platformId and contractAddress have no descriptions in the schema. The description compensates by explaining platformId is the chain (e.g., eth-ethereum) and contractAddress is the token address. The rationale parameter is fully documented in the 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 fetches current price and market data for a token by contract address, explicitly targeting on-chain and DeFi tokens. It also differentiates from getHistoricalTickerByContract, so an agent can distinguish it from siblings without inspecting schemas.

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?

It explicitly says to use this tool when a contract address is available rather than a name, and directs historical requests to getHistoricalTickerByContract. This gives concrete when-to-use and alternative guidance.

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

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

Need Help?