Skip to main content
Glama
Sign In
CoinPaprika MCP Server

CoinPaprika MCP Server

Official
by coinpaprika
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

getMappings

Cross-reference CoinPaprika IDs with external identifiers like CoinGecko, CoinMarketCap, ISIN, and DTI. Returns matching mapping rows or an empty list.

Instructions

Cross-reference CoinPaprika ids with external or legacy identifiers. Returns crosswalk rows linking a CoinPaprika id to its external ids; only matching rows return and no match returns an empty list. Use for 'map CoinPaprika id to CoinGecko', 'which coin is this CoinMarketCap id', 'find id for an ISIN'. Read-only. All params are optional string filters; provide at least one, extra filters narrow further: coinpaprika (a CoinPaprika id), coinmarketcap, coingecko, cryptocompare (each that provider's id), isin (an ISIN code), dti (a Digital Token Identifier). Requires a Business plan (COINPAPRIKA_API_KEY).

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

Input Schema

NameRequiredDescriptionDefault
dtiNoDTI to look up
isinNoISIN to look up
coingeckoNoCoinGecko ID to look up
coinpaprikaNoCoinPaprika ID to look up
coinmarketcapNoCoinMarketCap ID to look up
cryptocompareNoCryptoCompare ID to look up

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.7/5.0
Behavior4/5

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

The description discloses that the tool is read-only, returns only matching rows (empty list if none), and that all params are optional filters. Without annotations, this provides adequate behavioral transparency.

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?

The description is concise (few sentences), front-loaded with the main purpose, and contains no unnecessary words. 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 the tool's complexity (6 optional params, no output schema), the description covers purpose, behavior, parameter semantics, and usage examples. It explains return behavior and constraints completely.

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?

Schema coverage is 100% with descriptions for each parameter. The description adds value by explaining that params are filters, that providing at least one is necessary, and that extra filters narrow results. This clarifies usage beyond the schema.

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 tool is clearly named and the description states 'Cross-reference CoinPaprika ids with external or legacy identifiers', which is a specific verb and resource. It distinguishes itself from sibling tools that focus on single-entity data by emphasizing mapping between multiple identifiers.

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?

The description provides explicit use cases ('map CoinPaprika id to CoinGecko', 'which coin is this CoinMarketCap id', 'find id for an ISIN'), notes that params are optional but at least one should be provided, and mentions the Business plan requirement. This gives clear when-to-use guidance.

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