CoinPaprika

getContracts

Read-onlyIdempotent

List the token contract addresses tracked on one platform as a list, mapping each contract to its CoinPaprika coin id. Use for 'contracts on ethereum', 'what tokens does BSC have', or to map a contract address to a coin id. Find the platformId first with getPlatforms; for one contract's live price use getTickerByContract, and for its history use getHistoricalTickerByContract. Read-only. Params: platformId (required) is a platform id such as 'eth-ethereum' or 'bsc-binance-smart-chain'; limit (optional, default 50, max 250) caps how many contracts return. An unknown platformId returns an error. No API key required.

Input Schema

Name	Required	Description
`limit`	No
`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

Output Schema

Name	Required	Description	Default
`contracts`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 23, 2026

removedOutput schema / properties / contracts / items / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties / contracts / items / anyOf

Added value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "address": {
+        "description": "Contract address on the platform. Lowercase canonical for EVM; case-sensitive for Solana.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "CoinPaprika coin slug (e.g. 'usdc-usd-coin').",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "is_active": {
+        "type": [
+          "boolean",
+          "null"
+        ]
+      },
+      "name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "rank": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "symbol": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "type": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / contracts / items / properties

Removed value: -{
-  "address": {
-    "description": "Contract address on the platform. Lowercase canonical for EVM; case-sensitive for Solana.",
-    "type": "string"
-  },
-  "id": {
-    "description": "CoinPaprika coin slug (e.g. 'usdc-usd-coin').",
-    "type": "string"
-  },
-  "is_active": {
-    "type": "boolean"
-  },
-  "name": {
-    "type": "string"
-  },
-  "rank": {
-    "type": "number"
-  },
-  "symbol": {
-    "type": "string"
-  },
-  "type": {
-    "type": "string"
-  }
-}

removedOutput schema / properties / contracts / items / type
```
Removed value: -"object"
```

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": {
+    "contracts": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "address": {
+            "description": "Contract address on the platform. Lowercase canonical for EVM; case-sensitive for Solana.",
+            "type": "string"
+          },
+          "id": {
+            "description": "CoinPaprika coin slug (e.g. 'usdc-usd-coin').",
+            "type": "string"
+          },
+          "is_active": {
+            "type": "boolean"
+          },
+          "name": {
+            "type": "string"
+          },
+          "rank": {
+            "type": "number"
+          },
+          "symbol": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "contracts"
+  ],
+  "type": "object"
+}

First observedJul 28, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's 'Read-only' is largely redundant. It does add genuinely non-structured context: an unknown platformId returns an error, and no API key is required. It doesn't disclose result ordering or pagination behavior, which the output schema may partially cover.

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-loads what the tool returns before usage guidance, then siblings, then parameters — a sensible order with no filler sentences. Minor redundancy: 'Read-only' repeats the readOnlyHint annotation, and the description is on the long side for a two-parameter list tool.

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?

With an output schema present, return-value detail is unnecessary; the description instead supplies the prerequisite lookup, error behavior, rate/auth note, and limit bounds. An agent has everything it needs to invoke this correctly on the first try.

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 coverage is low (33%), and the description compensates by explaining platformId with concrete example values ('eth-ethereum', 'bsc-binance-smart-chain') and limit's default and maximum (50/250). The third parameter (rationale) is well documented in the schema itself, so nothing critical is left undocumented.

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 and resource — 'List the token contract addresses tracked on one platform' — and adds the mapping to CoinPaprika coin IDs, which is the distinguishing feature versus the ticker siblings. An agent can tell it apart from getTickerByContract and getHistoricalTickerByContract 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?

Provides concrete trigger phrasings ('contracts on ethereum', 'what tokens does BSC have'), plus a prerequisite ordering ('Find the platformId first with getPlatforms') and explicit alternatives for price and history use cases. Both when-to-use and which-sibling-to-use are spelled out.

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?