MCP Yahoo Finance
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_current_stock_priceC | Get the current stock price based on stock symbol. |
| get_stock_price_by_dateB | Get the stock price for a given stock symbol on a specific date. |
| get_stock_price_date_rangeC | Get the stock prices for a given date range for a given stock symbol. |
| get_historical_stock_pricesC | Get historical stock prices for a given stock symbol. |
| get_dividendsC | Get dividends for a given stock symbol. |
| get_income_statementC | Get income statement for a given stock symbol. |
| get_cashflowC | Get cashflow for a given stock symbol. |
| get_earning_datesC | Get earning dates. |
| get_newsC | Get news for a given stock symbol. |
| get_recommendationsC | Get analyst recommendations for a given symbol. |
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 10 tools
Most tools are clearly distinct, focusing on specific financial data types like cashflow, dividends, or news. However, there is some overlap between get_current_stock_price, get_stock_price_by_date, and get_stock_price_date_range, which could cause confusion about which to use for price queries, though their descriptions help clarify the differences.
All tools follow a consistent verb_noun pattern with 'get_' prefix and snake_case, such as get_cashflow and get_historical_stock_prices. This predictability makes it easy for agents to understand and navigate the tool set without naming conflicts or inconsistencies.
With 10 tools, the server is well-scoped for financial data retrieval, covering key aspects like prices, financial statements, news, and recommendations. Each tool serves a distinct purpose without being overly broad or sparse, fitting typical needs in this domain.
The tool set provides comprehensive coverage for retrieving financial data, including core elements like prices, statements, and news. A minor gap is the lack of tools for updating or managing data (e.g., no create or delete operations), but this is reasonable for a read-only finance server focused on data access.