Crypto MCP Server

get_token_price

Retrieve current price and market data for cryptocurrencies using CoinGecko token IDs, with support for multiple tokens and currency conversion.

Instructions

Get current price and market data for cryptocurrencies

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": {
      "tokenIds": "<tokenIds>"
    },
    "name": "get_token_price"
  }
}

Input Schema

Name	Required	Description	Default
`tokenIds`	Yes	CoinGecko token IDs (e.g., ["bitcoin", "ethereum", "solana"])
`vsCurrency`	No	Currency to convert to (default: "usd")	usd

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 13, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations provided, and the description does not disclose any behavioral traits (e.g., read-only, rate limits, error handling). It merely states the function without context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (one sentence), which is concise, but at the expense of completeness. It could include more detail without being verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema, the description should elaborate on the return format (e.g., price, market cap). It fails to provide enough context for a complete understanding of the tool's output.

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 covers all parameters with descriptions, so baseline is 3. The description adds no additional parameter information beyond what is already in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves price and market data for cryptocurrencies. It distinguishes from sibling tools like balance checkers and search, though it lacks specificity on what market data includes.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. For instance, it doesn't mention that for individual token balances, sibling tools like get_btc_balance should be used.

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

Deploy Server