CoinPaprika

getCapabilities

Read-onlyIdempotent

Get the server's capabilities, supported workflow patterns, validation rules and recommended tool sequences. Use FIRST to onboard as an agent, or when asked 'what can this server do', 'how should I chain these tools', 'what are the parameter rules'. This describes the MCP server itself, not crypto data.

Input Schema

Name	Required	Description	Default
`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
`api`	Yes
`note`	No
`server`	Yes
`plan_tiers`	Yes
`tools_count`	No
`coin_id_format`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedOct 23, 2026
- removedOutput schema / properties / api / additionalProperties
```
Removed value: -true
```
- addedOutput schema / properties / api / anyOf
```
Added value: +[
+  {
+    "additionalProperties": true,
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / api / properties
```
Removed value: -{}
```
- removedOutput schema / properties / api / type
```
Removed value: -"object"
```
- removedOutput schema / properties / coin_id_format / additionalProperties
```
Removed value: -true
```
- addedOutput schema / properties / coin_id_format / anyOf
```
Added value: +[
+  {
+    "additionalProperties": true,
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / coin_id_format / properties
```
Removed value: -{}
```
- removedOutput schema / properties / coin_id_format / type
```
Removed value: -"object"
```
- changedOutput schema / properties / note / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / plan_tiers / additionalProperties
```
Removed value: -true
```
- addedOutput schema / properties / plan_tiers / anyOf
```
Added value: +[
+  {
+    "additionalProperties": true,
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / plan_tiers / properties
```
Removed value: -{}
```
- removedOutput schema / properties / plan_tiers / type
```
Removed value: -"object"
```
- removedOutput schema / properties / server / additionalProperties
```
Removed value: -true
```
- addedOutput schema / properties / server / anyOf
```
Added value: +[
+  {
+    "additionalProperties": true,
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / server / properties
```
Removed value: -{}
```
- removedOutput schema / properties / server / type
```
Removed value: -"object"
```
- changedOutput schema / properties / tools_count / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```

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": {
+    "api": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    "coin_id_format": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    "note": {
+      "type": "string"
+    },
+    "plan_tiers": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    "server": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    "tools_count": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "server",
+    "api",
+    "plan_tiers"
+  ],
+  "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 establish readOnly, idempotent, openWorld, and non-destructive behavior. The description adds useful scope: it is an onboarding/capability-discovery tool that describes the server itself rather than crypto data, and it indicates the kind of information returned.

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?

Two tightly written sentences with no filler. The purpose is front-loaded, followed immediately by actionable usage guidance and a clear scope boundary.

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?

Given the rich parameter schema, output schema, and annotations, the description is complete enough for an agent to know when and why to call this tool. It also clarifies the non-crypto-data scope, which prevents confusion with sibling tools.

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?

The single rationale parameter has 100% schema description coverage, including detailed examples and constraints, so the schema carries parameter semantics. The tool description does not add further detail about the rationale parameter, so baseline 3 is appropriate.

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: get the server's capabilities, workflow patterns, validation rules, and recommended sequences. It explicitly distinguishes itself from sibling crypto-data tools by saying it describes the MCP server itself, not crypto data.

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 explicit usage conditions: use FIRST to onboard as an agent, or when asked what the server can do, how to chain tools, or what the parameter rules are. This directly routes the agent on when to choose this tool.

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?