CoinPaprika

keyInfo

Read-onlyIdempotent

Get details and usage for the CoinPaprika API key you supplied: plan, quota, requests remaining and expiry. Use for 'what plan am I on', 'how many requests are left', 'is my API key valid'. Read-only; takes no parameters. Requires you to supply your own paid-plan CoinPaprika key; without one this hosted server returns a plan-required message instead of calling the API. It reports your key, never the server's.

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": "keyInfo"
  }
}

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
`message`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026
RemovedOct 16, 2026

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": {
+    "message": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedJul 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false and openWorldHint=true, so the safety profile is given. Beyond that, the description adds real behavioral context an agent could not infer: the auth prerequisite (own paid-plan key), the degraded response mode (plan-required message rather than an API call), and the scoping guarantee that it reports the caller's key and not the server's. The one blemish is the claim that it "takes no parameters," which is behaviorally misleading given a required input.

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?

What it does is front-loaded in the first sentence, followed by short supporting sentences covering use cases, safety, prerequisites, and key scope. It is tight overall, but the incorrect "takes no parameters" clause spends words on a claim that is at best wasted and at worst harmful.

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?

With an output schema present, the description needn't explain return values, and annotations cover the safety profile, so the remaining burden is auth and failure-mode disclosure, which it handles well. The only material omission is any mention of the required `rationale` argument, which for a one-parameter tool is a notable gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single required `rationale` parameter, which would normally justify a baseline 3. However, the description asserts the tool "takes no parameters," actively contradicting the schema and risking a failed or malformed call if the agent omits the required rationale. That inaccuracy drops it below baseline.

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 opens with a specific verb+resource ("Get details and usage for the CoinPaprika API key you supplied") and enumerates the returned fields (plan, quota, requests remaining, expiry), so an agent knows exactly what this does. No sibling tool covers key/credential status, and the framing ("your key, never the server's") distinguishes it from quota-adjacent tools like status.

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 gives concrete triggering user phrasings ("what plan am I on", "how many requests are left", "is my API key valid") and states the condition under which the tool will not perform its job: without a paid-plan key the hosted server returns a plan-required message instead of calling the API. That covers both when-to-use and when-not, which is more than most definitions supply.

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?