coincap-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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bitcoin_priceB | Get realtime bitcoin price |
| get_crypto_priceC | Get realtime crypto price on crypto |
| list_assetsB | Get all available crypto assets |
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 3 tools
Two tools (bitcoin_price and get_crypto_price) have overlapping purposes, both focused on fetching crypto prices, which creates ambiguity. The descriptions do not clearly differentiate them, making it likely an agent could misselect between them. The third tool (list_assets) is distinct, but the overlap between the first two significantly reduces clarity.
The naming is mixed, with two tools using a verb_noun pattern (get_crypto_price, list_assets) and one using a noun_verb pattern (bitcoin_price). While readable, this inconsistency in verb placement and specificity (bitcoin vs. crypto) deviates from a predictable convention. The patterns are not chaotic but lack uniformity.
With 3 tools, the count is borderline thin for a crypto data server, as it may lack comprehensive coverage for common operations like historical data or multiple asset queries. However, it is reasonable for a minimal or focused scope, though it feels slightly under-scoped for typical crypto API use cases.
The tool set has significant gaps for a crypto data domain, such as missing operations for historical price data, market cap info, volume, or specific asset details beyond listing. The overlap in price tools does not add functionality, and agents may struggle with incomplete workflows like tracking trends or comparing assets over time.