Skip to main content
Glama
leoncuhk

MCP Yahoo Finance

by leoncuhk
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_historical_stock_prices

Retrieve historical stock price data for analysis by specifying a stock symbol, time period, and data interval through the MCP Yahoo Finance server.

Instructions

Get historical stock prices for a given stock symbol.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesStock symbol in Yahoo Finance format.
periodNoThe period for historical data. Defaults to "1mo". Valid periods: "1d", "5d", "1mo", "3mo", "6mo", "1y", "2y", "5y", "10y", "ytd", "max"
intervalNoThe interval beween data points. Defaults to "1d". Valid intervals: "1d", "5d", "1wk", "1mo", "3mo"

Implementation Reference

  • src/mcp_yahoo_finance/server.py:231-248 (handler)
    MCP tool handler registered with @mcp_instance.tool(), defines input schema via type annotations and docstring, executes by delegating to YahooFinance instance method.
    @mcp_instance.tool()
def get_historical_stock_prices(
    symbol: str,
    period: Literal[
        "1d", "5d", "1mo", "3mo", "6mo", "1y", "2y", "5y", "10y", "ytd", "max"
    ] = "1mo",
    interval: Literal["1d", "5d", "1wk", "1mo", "3mo"] = "1d",
) -> str:
    """Get historical stock prices for a given stock symbol.

    Args:
        symbol (str): Stock symbol in Yahoo Finance format.
        period (str): The period for historical data. Defaults to "1mo".
                Valid periods: "1d", "5d", "1mo", "3mo", "6mo", "1y", "2y", "5y", "10y", "ytd", "max"
        interval (str): The interval beween data points. Defaults to "1d".
                Valid intervals: "1d", "5d", "1wk", "1mo", "3mo"
    """
    return yf_instance.get_historical_stock_prices(symbol, period, interval)
  • src/mcp_yahoo_finance/server.py:67-89 (helper)
    Core helper method in YahooFinance class that implements the logic to fetch historical stock prices using yfinance Ticker.history() and formats as JSON.
    def get_historical_stock_prices(
    self,
    symbol: str,
    period: Literal[
        "1d", "5d", "1mo", "3mo", "6mo", "1y", "2y", "5y", "10y", "ytd", "max"
    ] = "1mo",
    interval: Literal["1d", "5d", "1wk", "1mo", "3mo"] = "1d",
) -> str:
    """Get historical stock prices for a given stock symbol.

    Args:
        symbol (str): Stock symbol in Yahoo Finance format.
        period (str): The period for historical data. Defaults to "1mo".
                Valid periods: "1d", "5d", "1mo", "3mo", "6mo", "1y", "2y", "5y", "10y", "ytd", "max"
        interval (str): The interval beween data points. Defaults to "1d".
                Valid intervals: "1d", "5d", "1wk", "1mo", "3mo"
    """
    stock = Ticker(ticker=symbol, session=self.session)
    prices = stock.history(period=period, interval=interval)

    if hasattr(prices.index, "date"):
        prices.index = prices.index.date.astype(str)  # type: ignore
    return f"{prices['Close'].to_json(orient='index')}"

Tool Definition Quality

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't describe how it behaves: there's no information about data format, pagination, rate limits, error handling, or authentication requirements. For a data-fetching tool with zero annotation coverage, this leaves significant gaps in understanding its operational characteristics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that communicates the core purpose without unnecessary words. It's appropriately sized for a straightforward data retrieval tool and front-loads the essential information immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of annotations and output schema, the description is incomplete for a tool with three parameters. While it states the purpose clearly, it doesn't address behavioral aspects like return format, data structure, or error conditions that would help an agent use it correctly. The schema handles parameters well, but overall context for invocation is lacking.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with all three parameters well-documented in the schema itself (symbol format, period options with defaults, interval options with defaults). The description adds no additional parameter information beyond what's already in the schema, so it meets the baseline of 3 where the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and resource 'historical stock prices' with the target 'for a given stock symbol', making the purpose immediately understandable. It distinguishes from siblings like 'get_current_stock_price' by specifying 'historical' data, though it doesn't explicitly contrast with other historical tools like 'get_stock_price_by_date' or 'get_stock_price_date_range'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With multiple sibling tools for stock data (e.g., 'get_current_stock_price', 'get_stock_price_by_date', 'get_stock_price_date_range'), there's no indication of when this historical price tool is preferred over others or what specific use cases it serves.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/leoncuhk/mcp-yahoo-finance'

If you have feedback or need assistance with the MCP directory API, please join our Discord server