Yahoo Finance MCP Server

get_price_history

Fetch historical price data for any stock symbol using custom time periods and intervals, enabling trend analysis and data-driven decisions.

Instructions

Fetch historical price data for a given stock symbol over a specified period and interval.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`period`	No	Time period to retrieve data for (e.g. '1d', '1mo', '1y').	1mo
`symbol`	Yes	The stock symbol
`interval`	No	Data interval frequency (e.g. '1d', '1h', '1m')	1d
`chart_type`	No	Type of chart: 'price_volume' for candlestick with volume bars, 'vwap' for Volume Weighted Average Price, or 'volume_profile' for volume distribution by price level

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Sep 6, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description must carry behavioral disclosure, and it does at least make clear this is a read-only fetch rather than a mutation. However, it omits caveats such as valid period/interval combinations, data limitations, or rate-limit behavior, leaving meaningful gaps.

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?

One sentence, front-loaded with the action, with no filler or repetition of schema details. It is as concise as a tool description can be.

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

Completeness4/5

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

For a simple data-fetch tool, the description plus the complete input schema and output schema cover the essential calling context. The main omissions are behavioral caveats and routing guidance, which are already reflected in other dimensions.

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%, so the description only needs to add extra context; it mentions period and interval but merely restates their names. It does not warn about important interactions like intraday intervals being usable only for recent periods.

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

Purpose5/5

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

The description starts with a specific verb and object ('Fetch historical price data') and scopes it to a stock symbol with a period and interval. This cleanly separates it from the news, info, search, and top-list siblings.

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

Usage Guidelines4/5

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

The tool's intended use is easy to infer: call it whenever historical price series are needed for a symbol. It does not explicitly name when not to use it or mention alternatives, but the context is sufficiently clear.

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

Deploy Server