Fetch historical price data for up to 25 symbols in one batch. Provide start/end dates or period to retrieve clean JSON for finance analysis.
Yahoo Finance batch historical prices. Returns historical price data for up to 25 symbols.
| Name | Required | Description | Default |
|---|---|---|---|
| request | Yes | Batch download request |
Changes observed during successful MCP inspections.
v1.17.5Input schema / properties / request / propertiesAdded value: +{
+ "auto_adjust": {
+ "type": "boolean"
+ },
+ "back_adjust": {
+ "type": "boolean"
+ },
+ "end": {
+ "type": "string"
+ },
+ "include_actions": {
+ "type": "boolean"
+ },
+ "include_prepost": {
+ "type": "boolean"
+ },
+ "interval": {
+ "type": "string"
+ },
+ "keepna": {
+ "type": "boolean"
+ },
+ "period": {
+ "type": "string"
+ },
+ "rounding": {
+ "type": "boolean"
+ },
+ "start": {
+ "type": "string"
+ },
+ "symbols": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ }
+}Input schema / properties / request / requiredAdded value: +[
+ "symbols"
+]v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden, but it only reveals that historical price data is returned. It does not disclose defaults for period/interval, adjustment behavior, date range handling, error cases, or output format—important behaviors for a data-download tool. This is a significant transparency gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short, front-loaded sentences deliver the core function and the key constraint (25-symbol limit) with no wasted words. Every clause earns its place, and the structure makes the tool's purpose immediately scannable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with a nested request object, many undocumented parameters, no output schema, and no annotations, this description is clearly incomplete. An agent lacks critical information about date formats, default intervals, adjustment flags, or expected return shape, making correct invocation guesswork despite the clear purpose.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema exposes many domain-specific parameters (period, interval, auto_adjust, back_adjust, keepna, etc.) with no individual descriptions, and the only schema description is the tautological 'Batch download request'. The tool description adds no meaning to these parameters, leaving the agent without guidance on valid values or combinations.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific operation ('Returns historical price data') and a clear resource scope (Yahoo Finance batch historical prices, up to 25 symbols). It distinguishes itself from single-ticker siblings like yahoo_finance_ticker_history by emphasizing the batch capability, so an agent can tell them apart.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The word 'batch' and the 'up to 25 symbols' limit imply this tool is for multi-symbol historical data retrieval, giving some usage context. However, it does not explicitly state when to prefer this over alternatives like yahoo_finance_ticker_history or google_finance_chart, nor does it mention exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.