Price Service 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_priceC | Get cryptocurrency price data from the price service |
| health_checkB | Check the health status of the price service |
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 2 tools
The two tools have completely distinct purposes: get_price retrieves cryptocurrency price data, while health_check monitors the service's operational status. There is no overlap or ambiguity in their functions, making it easy for an agent to select the correct tool for each task.
Both tools follow a consistent verb_noun naming pattern (get_price, health_check), using clear and descriptive verbs that align with their actions. The naming is uniform and predictable across the tool set.
With only two tools, the server feels under-scoped for a price service domain. While get_price is essential, the tool set lacks operations like historical price retrieval, multi-asset queries, or market data analysis, making it too limited for typical cryptocurrency price service workflows.
The tool set is severely incomplete for a cryptocurrency price service. It includes basic price fetching and health monitoring but misses critical operations such as historical price data, price comparisons, or support for multiple cryptocurrencies, which are standard expectations in this domain.