Skip to main content
Glama

Fintel Discovery — Financial Intelligence for AI Agents

Get Price History (OHLCV)

GetPriceHistory
Read-onlyIdempotent
    Fetch OHLCV (Open, High, Low, Close, Volume) price history for one ticker.
    Returns daily, weekly, monthly, or intraday bars over any period.

    Use this tool when:
    - You need historical price or volume data for a stock, ETF, or crypto
    - You want to analyze performance over a specific time range
    - You need to compute returns, volatility, or trend analysis

    Interval options: 1d (daily), 1wk (weekly), 1mo (monthly),
    1h (hourly, max 730 days), 5m/15m/30m (intraday, max 60 days).
    Period options: 1mo, 3mo, 6mo, 1y, 2y, 5y, 10y, ytd, max.

    Source: Yahoo Finance via yfinance. No API key required.
    

Input Schema

NameRequiredDescriptionDefault
paramsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $defs / PriceHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"498d9131-d794-4dd2-b1d6-b4d19d83cf35"New value: +"1e3db2ac-608d-4ff7-8b19-8fc78826e993"
  2. Changed1 schema field changed
    • changedInput schema / $defs / PriceHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"05525087-35e9-4aac-b06d-6d88ce386b2e"New value: +"498d9131-d794-4dd2-b1d6-b4d19d83cf35"
  3. Changed1 schema field changed
    • changedInput schema / $defs / PriceHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"f258bd16-f060-4e4a-a55d-221a0484866d"New value: +"05525087-35e9-4aac-b06d-6d88ce386b2e"
  4. Changed1 schema field changed
    • changedInput schema / $defs / PriceHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"5f4db44b-e5cc-4f3a-8da3-ac591a019c81"New value: +"f258bd16-f060-4e4a-a55d-221a0484866d"
  5. Changed1 schema field changed
    • changedInput schema / $defs / PriceHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"d9f77642-e017-4785-9150-e658c2dba3a0"New value: +"5f4db44b-e5cc-4f3a-8da3-ac591a019c81"
  6. Changed1 schema field changed
    • changedInput schema / $defs / PriceHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"dbe99169-c071-4ed4-9ae9-8bbfb9a88ad8"New value: +"d9f77642-e017-4785-9150-e658c2dba3a0"
  7. Changed1 schema field changed
    • changedInput schema / $defs / PriceHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"3775b46a-5aa8-4586-af57-2453c8bcd08c"New value: +"dbe99169-c071-4ed4-9ae9-8bbfb9a88ad8"
  8. Changed1 schema field changed
    • changedInput schema / $defs / PriceHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"d81a5175-11e9-494a-baa5-71d4ffad4ab9"New value: +"3775b46a-5aa8-4586-af57-2453c8bcd08c"
  9. Changed1 schema field changed
    • changedInput schema / $defs / PriceHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"9e7f8798-7d22-4378-b93d-179c6f8cb854"New value: +"d81a5175-11e9-494a-baa5-71d4ffad4ab9"
  10. Changed1 schema field changed
    • changedInput schema / $defs / PriceHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"9919ff85-e960-472f-863b-3de4c5abed9f"New value: +"9e7f8798-7d22-4378-b93d-179c6f8cb854"
  11. Changed1 schema field changed
    • changedInput schema / $defs / PriceHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"38452924-d5df-4668-b51c-d7cd5acabc09"New value: +"9919ff85-e960-472f-863b-3de4c5abed9f"
  12. Changed1 schema field changed
    • changedInput schema / $defs / PriceHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"fa72f604-6239-428b-81df-11f07c2c8d00"New value: +"38452924-d5df-4668-b51c-d7cd5acabc09"
  13. Changed1 schema field changed
    • changedInput schema / $defs / PriceHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"7b866f24-13ab-4e54-8d3a-f775612c393f"New value: +"fa72f604-6239-428b-81df-11f07c2c8d00"
  14. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive behavior, and the description is consistent with that. It adds useful behavioral context: Yahoo Finance source, no API key, and interval-specific maximum lookbacks. Return shape is not described, but an output schema exists.

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?

Front-loads the action and result, then uses short bullets for usage and compact option lists. Every section contributes directly to selecting or configuring the tool.

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?

Given the output schema and read-only annotations, the description is complete enough for an agent to call the tool for standard price-history requests. Minor gaps remain around date-range parameters and adjustment behavior, but they do not block correct core use.

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?

The description explains interval and period options, including intraday and hourly max ranges, which is useful for the core query parameters. However, it does not explain start/end override behavior, auto_adjust, actions, or the additional internal filter parameters, so it only partially compensates for the reported low schema description coverage.

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 and resource: 'Fetch OHLCV price history for one ticker.' The 'one ticker' scope also distinguishes it from sibling GetMultiTickerHistory, so the agent can select it without opening the schema.

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?

Includes explicit 'Use this tool when' bullets covering historical price/volume data, time-range analysis, and returns/volatility/trend computation. It does not name when-not-to-use or an explicit alternative, so it is clear but not fully routing.

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