CoinPaprika

getCoins

Read-onlyIdempotent

List all available coins with id, name, symbol and rank. Use to discover coins or map a name to an id. Does NOT include prices; for prices use getTickers or getTickersById. Read-only; limit caps the number of coins returned. No API key required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rationale": "<rationale>"
    },
    "name": "getCoins"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Optional. Items per page (default 50, max 250). Server clamps requests above 250.
`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.

Output Schema

Name	Required	Description	Default
`coins`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 23, 2026

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

addedOutput schema / properties / coins / items / anyOf

Added value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "id": {
+        "description": "CoinPaprika coin slug, format symbol-name (e.g. 'btc-bitcoin').",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "is_active": {
+        "type": [
+          "boolean",
+          "null"
+        ]
+      },
+      "is_new": {
+        "type": [
+          "boolean",
+          "null"
+        ]
+      },
+      "name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "rank": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "symbol": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "type": {
+        "description": "'coin' or 'token'.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / coins / items / properties

Removed value: -{
-  "id": {
-    "description": "CoinPaprika coin slug, format symbol-name (e.g. 'btc-bitcoin').",
-    "type": "string"
-  },
-  "is_active": {
-    "type": "boolean"
-  },
-  "is_new": {
-    "type": "boolean"
-  },
-  "name": {
-    "type": "string"
-  },
-  "rank": {
-    "type": "number"
-  },
-  "symbol": {
-    "type": "string"
-  },
-  "type": {
-    "description": "'coin' or 'token'.",
-    "type": "string"
-  }
-}

removedOutput schema / properties / coins / 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": {
+    "coins": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "id": {
+            "description": "CoinPaprika coin slug, format symbol-name (e.g. 'btc-bitcoin').",
+            "type": "string"
+          },
+          "is_active": {
+            "type": "boolean"
+          },
+          "is_new": {
+            "type": "boolean"
+          },
+          "name": {
+            "type": "string"
+          },
+          "rank": {
+            "type": "number"
+          },
+          "symbol": {
+            "type": "string"
+          },
+          "type": {
+            "description": "'coin' or 'token'.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "coins"
+  ],
+  "type": "object"
+}

First observedJul 28, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/destructive, so the description correctly focuses on complementary facts: no API key required, and that limit caps the result count. What it doesn't disclose is pagination behavior or what happens past the first page, which for a list tool is the remaining behavioral gap.

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?

Four short clauses, front-loaded with the resource and return fields, then the exclusion, then operational facts. Every sentence carries distinct information with no restatement of the name.

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?

Output schema exists, so return values need no explanation; annotations carry the safety profile and the schema carries the parameter detail. The description fills the remaining slots – purpose, routing, and auth/limit context – with nothing material missing.

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 coverage is 100%, with limit fully documented (default 50, max 250, server clamp) and rationale also documented. The description's 'limit caps the number of coins returned' is consistent but adds nothing beyond the schema, so baseline 3 applies.

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?

Specific verb+resource ('List all available coins') plus the exact fields returned (id, name, symbol, rank). It also explicitly carves out the price data domain, which separates it from the getTickers* siblings without needing to open their 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?

States both when to use it ('discover coins or map a name to an id') and when not to ('Does NOT include prices; for prices use getTickers or getTickersById'), naming the concrete alternatives. No inference required.

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?