Skip to main content
Glama
CoinPaprika MCP Server

CoinPaprika MCP Server

Official

keyInfo

Retrieve current CoinPaprika API key details—plan, quota, remaining requests, and expiry—to verify validity and track usage. Read-only; requires a configured paid-plan key.

Instructions

Get details and usage for the current CoinPaprika API key: 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 a configured COINPAPRIKA_API_KEY on a paid plan (Starter or higher); without a key the call is rejected.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "keyInfo"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description must carry the full load, and it does most of it: declares read-only, zero parameters, the required credential and plan tier, and the rejection behavior when no key exists. It does not say whether the call itself consumes quota or how the rejection surfaces (error code vs empty result).

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 sentences, front-loaded with the capability and return fields, then intents, then the auth constraint. Every sentence adds information an agent would otherwise have to guess.

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?

No output schema exists, so the description compensates by listing the four returned values and the auth precondition. The only meaningful omission is the failure-mode shape (how a rejected call appears) and whether the read counts against quota.

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?

Zero parameters, so the baseline is 4. The description explicitly confirms 'takes no parameters', matching the empty schema, so there is no risk of an agent inventing arguments.

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 ('Get details and usage') plus a precisely scoped resource ('the current CoinPaprika API key'), with the returned fields enumerated (plan, quota, requests remaining, expiry). No sibling tool touches key metadata, so an agent can route here without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Three quoted user intents ('what plan am I on', 'how many requests are left', 'is my API key valid') give strong routing signals, and the prerequisite (configured COINPAPRIKA_API_KEY on a paid plan) defines the case where the tool fails. It stops short of naming an alternative for when no key is configured, but no sibling covers that gap either.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.