Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_ticker_history

Fetch historical price data for a Yahoo Finance symbol, including open, high, low, close, adjusted close, volume, dividends, and splits by period or date range.

Instructions

Yahoo Finance historical prices. Returns price points for a Yahoo Finance symbol: open, high, low, close, adjusted close and volume with timestamps. Use period (default 1mo, up to max) or start and end, which override it. interval sets the candle size (default 1d; intraday covers recent ranges only). include_actions adds dividend, split and capital-gain events.

Input Schema

NameRequiredDescriptionDefault
endNoUnix seconds, RFC3339, or YYYY-MM-DD
startNoUnix seconds, RFC3339, or YYYY-MM-DD
keepnaNoKeep fully empty chart rows
periodNoRange such as 1d, 1mo, 1y, max
symbolYesYahoo Finance symbol such as AAPL
intervalNoInterval such as 1d, 1h, 5m
roundingNoRound prices to two decimals
auto_adjustNoAdjust OHLC prices with adjusted close
back_adjustNoBack-adjust OHLC prices while keeping close
include_actionsNoInclude dividends, splits, and capital gains
include_prepostNoInclude pre/post market data

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses useful defaults (period 1mo, interval 1d), the max cap, and the intraday limitation, but says nothing about auth, rate limits, or how auto_adjust/back_adjust alter the returned series — real behavioral gaps for a market-data call.

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

Conciseness4/5

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

Front-loaded with the purpose, then parameter behavior, with essentially no filler. The backtick-heavy style is dense but every clause carries information; slightly packed sentences keep it from a 5.

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

Completeness3/5

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

For an 11-parameter tool with no output schema and no annotations, the description covers the core return fields and the main timing parameters adequately. It leaves the adjustment flags (auto_adjust, back_adjust), keepna, and rounding to the schema, and offers no return-structure detail, so it is only minimally complete.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description exceeds it by adding default values (period=1mo, interval=1d), the override precedence of start/end over period, and the effect of include_actions. These are semantic details the schema alone does not convey.

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?

States a specific verb+resource ('Yahoo Finance historical prices') and enumerates the returned fields (open, high, low, close, adjusted close, volume with timestamps), so the agent knows exactly what the tool produces. It does not explicitly distinguish itself from close siblings like yahoo_finance_download or yahoo_finance_ticker_history_metadata, which keeps it from a 5.

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

Usage Guidelines3/5

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

It explains the period-vs-start/end relationship ('start and end, which override it') and the intraday range constraint, which is genuine usage guidance for the parameters. However, it gives no when-to-use/when-not guidance relative to alternative Yahoo Finance tools, so usage is only implied.

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

Deploy Server

Other Tools