Stock 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_stock_priceA | Get real-time stock price information for a given ticker symbol. Returns last price, timestamp, market state (PRE/REGULAR/AFTER/POST/CLOSED), and currency. |
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_stock_price' has a clearly distinct purpose that cannot be confused with any other tool in this set.
The naming pattern cannot be inconsistent when there is only one tool. The tool name 'get_stock_price' follows a clear verb_noun convention that would be consistent if more tools existed.
A single tool is generally too few for a server's purpose unless it's extremely narrow. For a stock price server, one might expect additional tools like historical data, multiple tickers, or market indicators, making this feel thin and limited in scope.
The server is severely incomplete for a stock price domain. While it provides real-time prices, it lacks essential operations such as historical price data, volume information, company details, or batch queries for multiple stocks, which are common in financial applications.