Asset Price MCP Server
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 |
|---|---|
| get_asset_priceB | Retrieves current pricing information for various assets including precious metals and cryptocurrencies |
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 ambiguity or overlap between tools. The single tool 'get_asset_price' has a clearly defined purpose that cannot be confused with any other tool in this set.
The single tool name follows a clear verb_noun pattern ('get_asset_price'), and with only one tool, there is perfect consistency. There are no other tools to create naming conflicts or inconsistencies.
A single tool is too few for a server named 'Asset Price MCP Server', which suggests a broader scope for asset price operations. While the tool covers current pricing, the server lacks tools for historical data, price comparisons, or other related functions, making it feel thin and under-scoped.
The server is severely incomplete for an asset price domain. It only provides current pricing with no tools for historical prices, price alerts, asset lists, or market data analysis. This creates significant gaps that will limit agent functionality and cause failures in more complex tasks.