CryptoPriceTracker-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_crypto_priceA | Get the current price of a cryptocurrency in a specified currency using the CoinGecko API. Args: cryptocurrency: The id of the cryptocurrency (e.g., 'bitcoin', 'ethereum'). currency: The fiat or crypto currency to convert to (e.g., 'usd', 'inr'). Returns: The current price as a float. Returns 0.0 if the price cannot be fetched. Example: get_crypto_price(cryptocurrency="bitcoin", currency="usd") get_crypto_price(cryptocurrency="ethereum", currency="inr") |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of confusion or misselection between tools. Its purpose is singular and clearly stated.
The sole tool name get_crypto_price follows a clear and predictable verb_noun snake_case convention. With only one tool, there is no inconsistency to penalize.
A single tool is borderline thin for a server named CryptoPriceTracker-MCP. It can fetch a current price, but the scope suggests more functionality could reasonably be expected.
The surface only supports fetching a single current price. Obvious adjacent operations such as historical prices, price ranges, supported currency lists, or market data are missing, creating significant gaps for a crypto price tracking domain.