Crawlora MCP

yahoo_finance_download

Read-only

Fetch historical OHLC price records for up to 25 Yahoo Finance symbols in one request. Set symbols and use start/end or period plus interval to choose dates and cadence; adjustment flags control corporate-action handling. Use yahoo_finance_ticker_history for one symbol or yahoo_finance_ticker_history_metadata to inspect valid ranges and intervals.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "yahoo_finance_download"
  }
}

Input Schema

Name	Required	Description
`end`	No	End date (exclusive) as YYYY-MM-DD or a Unix timestamp. Defaults to now.
`start`	No	Start date (inclusive) as YYYY-MM-DD or a Unix timestamp. Overrides period when set.
`keepna`	No	Keep rows that contain NaN/null values. Default false.
`period`	No	Time range. Allowed values: 1d, 5d, 1mo, 3mo, 6mo, 1y, 2y, 5y, 10y, ytd, max. Default 1mo. Ignored when start is set.
`symbols`	No	List of ticker symbols to download, e.g. [AAPL, MSFT]. Required, up to 25 symbols.
`interval`	No	Candle interval. Allowed values: 1m, 2m, 5m, 15m, 30m, 60m, 90m, 1h, 1d, 5d, 1wk, 1mo, 3mo. Default 1d.
`rounding`	No	Round prices to the symbol's display precision. Default false.
`auto_adjust`	No	Adjust OHLC prices for dividends and splits. Default false.
`back_adjust`	No	Back-adjust prices using dividend and split data. Default false.
`include_actions`	No	Include dividends, splits, and capital gains events. Default false.
`include_prepost`	No	Include pre-market and post-market data points. Default false.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly and openWorld, so the safety profile is covered. The description adds real behavioral context: the 25-symbol cap and that adjustment flags govern corporate-action handling. It omits rate limits or failure modes, keeping it just short of a 5.

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?

Two dense sentences, no filler: the first establishes what and the limit, the second covers parameter mechanics and sibling routing. Front-loaded and every clause earns its place.

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

Completeness5/5

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

With a fully documented 11-param schema, an output schema covering return values, and annotations covering the safety profile, the description supplies everything an agent needs to select and invoke the tool correctly.

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 every parameter already documents its format, defaults, precedence rules and allowed values. The description groups the parameters logically (dates vs. cadence vs. adjustment flags) but adds no syntax detail beyond the schema.

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?

States a specific verb (Fetch), resource (historical OHLC price records), and scope (up to 25 symbols in one request). It also distinguishes itself from yahoo_finance_ticker_history and yahoo_finance_ticker_history_metadata by name.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use yahoo_finance_ticker_history for a single symbol, and yahoo_finance_ticker_history_metadata to inspect valid ranges and intervals. The condition selecting this tool (multi-symbol batch download) is made clear.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?