MCP Stock Tracker
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALPHA_VANTAGE_API_KEY | Yes | Alpha Vantage API key for fetching stock data. |
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": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_stock_quoteA | Get real-time stock quote for a symbol Args: symbol: Stock ticker symbol (e.g., AAPL, MSFT, GOOGL) Returns: Dictionary containing stock quote data including price, change, volume, etc. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| stock_tracker | Real time stock tracker |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion. The tool's purpose is clearly defined for retrieving a stock quote.
The single tool name follows a clear verb_noun pattern (get_stock_quote), which is consistent and readable. However, with only one tool, pattern consistency across multiple tools cannot be fully assessed.
One tool is insufficient for a stock tracker. Users would expect additional functionality such as symbol lookup, historical data, or portfolio management, making the count feel overly minimal.
The tool surface is severely incomplete. A stock tracker should at least include listing available symbols or fetching historical prices, but only a single quote retrieval is provided.