Skip to main content
Glama

Crawlora MCP

yahoo_finance_ticker_history

Read-only

Fetch historical Yahoo Finance share prices by symbol, including date-stamped OHLCV points (open, high, low, close, adjusted close, and volume). Use period=max with a daily interval for the full available price history; explicit start/end dates override period. Read-only; hosted calls require a Crawlora API key and may consume credits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "yahoo_finance_ticker_history"
  }
}

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.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful context beyond them: that hosted calls need a Crawlora API key and may consume credits, which affects how an agent should budget calls.

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?

Three sentences, no filler: what is returned first, then the period/date guidance, then the auth/credit caveat. Front-loaded and every sentence earns its place.

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?

An output schema exists so return values need not be re-explained, and the description still summarizes them. Auth/credit and date-vs-period semantics are covered; only finer details like default interval are left implicit, which is acceptable for an 11-param read-only tool.

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 baseline is 3, but the description adds real semantics the schema lacks: the period=max/daily-interval combination and the start/end-overrides-period precedence rule, which is decision-relevant. Default interval and symbol-format behavior remain unstated.

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) and resource (historical Yahoo Finance share prices) and enumerates the returned fields (OHLCV plus adjusted close). An agent immediately knows this is the price-history endpoint, distinguishable from siblings like yahoo_finance_ticker_actions or ticker_info.

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?

Explains the period=max + daily interval pattern for full history and the precedence rule that explicit start/end override period. It does not name competing siblings (e.g. download vs history_metadata), so routing guidance is contextual rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources