crypto_price_tracker
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_market_infoA | |
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
With only one tool, there is no possibility of confusing it with another. The tool's purpose is clearly defined and distinct.
The single tool follows a clear verb_noun pattern ('get_crypto_market_info'), which is consistent with standard naming conventions and leaves no room for inconsistency.
The server has only one tool, which is extremely thin for a typical MCP server. A crypto price tracker would typically need additional capabilities such as historical data, symbol discovery, or alerts to be useful.
The tool covers the core need of fetching current exchange rates, but it lacks obvious complementary features like historical data or a way to list supported cryptocurrencies, leaving notable gaps for a price tracking domain.