Stock Market 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_ticker_priceB | Get current price for a stock ticker |
| get_market_reportB | Generate US market report/briefing |
| get_financial_statementC | Get financial statements for a company |
| get_company_overviewC | Get company overview and key metrics |
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 4 tools
Each tool has a clearly distinct purpose: company overview, financial statements, market report, and stock price. There is no overlap in functionality, making it easy for an agent to select the right tool for each specific need without confusion.
All tool names follow a consistent verb_noun pattern with 'get_' prefix, using snake_case uniformly. This predictability enhances readability and usability across the tool set.
With 4 tools, the server is well-scoped for basic stock market data retrieval, though it might benefit from additional tools like historical price data or news feeds. The count is reasonable and each tool earns its place in the domain.
The tools cover key retrieval operations for company and market data, but there are notable gaps such as lack of update, delete, or analysis tools (e.g., technical indicators, portfolio management). This limits the server to read-only use cases.