Skip to main content
Glama
Sign In
CoinPaprika MCP Server

CoinPaprika MCP Server

Official
by coinpaprika
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

getTickers

Retrieve current prices, market caps, and 24-hour changes for top cryptocurrencies ranked by market cap. Provides a market snapshot with optional quote currencies and limit.

Instructions

Get current prices, market caps and 24h changes for the top cryptocurrencies ranked by market cap. Use for 'top 5 coins', 'top crypto today', 'biggest cryptocurrencies', or a market snapshot. For one specific coin use getTickersById. Read-only; quotes sets the quote currencies (default USD), limit caps results. No API key required.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of tickers to return (default: 50, max: 250)
quotesNoComma-separated quote currencies (e.g., USD,BTC,ETH)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations provided, so description bears full burden. It describes read-only nature, parameter roles (quotes default USD, limit caps results). Could add further details like rate limits or response structure but overall adequate.

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 sentences, no redundancy, front-loaded with purpose and usage. Every sentence adds value.

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 2 optional params, no output schema, no annotations, description sufficiently covers usage, parameter behavior, and safety (read-only). Agent can confidently invoke.

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 descriptions for both parameters. Description adds default for quotes and clarifies that limit caps results. However, it doesn't add substantial meaning beyond schema, so baseline 3.

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 clearly states the tool retrieves current prices, market caps, and 24h changes for top cryptocurrencies by market cap. It provides specific verb 'Get' and resource, and distinguishes from sibling getTickersById.

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?

Explicitly lists use cases like 'top 5 coins', 'top crypto today', and advises using getTickersById for single coins. Also mentions no API key needed.

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

Deploy Server

Other Tools