Financial Data MCP Server

Get Historical Prices Tool

get_historical_prices_tool

Retrieve historical OHLC price data for any stock ticker across periods from one day to ten years to analyze price trends and performance.

Instructions

Get historical OHLC (Open/High/Low/Close) price data for a ticker.

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": {
      "ticker": "<ticker>"
    },
    "name": "get_historical_prices_tool"
  }
}

Input Schema

Name	Required	Description	Default
`period`	No	One of "1d","5d","1mo","3mo","6mo","1y","2y","5y","10y","ytd","max". Defaults to "1mo".	1mo
`ticker`	Yes	Exact stock ticker symbol, e.g. "AAPL".

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the kind of data returned (OHLC) and does not describe ordering, adjustment behavior, timezone handling, error behavior, or whether the operation is strictly read-only beyond the verb 'Get'.

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?

The description is a single front-loaded sentence with no filler. Every word contributes to identifying the resource and data type.

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?

For a simple two-parameter retrieval tool with complete schema documentation and an output schema present, the description is adequate to enable invocation. It does not cover usage distinctions or behavioral edge cases, but those are covered in other dimensions and the tool name/sibling context supplies additional orientation.

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%, with ticker and period both documented in the input schema, including permitted period values and the default. The description itself adds no parameter-level meaning beyond mentioning 'ticker', so the baseline of 3 applies.

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?

The description uses a specific verb and resource: 'Get historical OHLC price data for a ticker.' It clearly distinguishes this tool from sibling tools like get_stock_quote_tool (current quote vs historical) and get_company_overview_tool (fundamentals vs price data).

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?

The word 'historical' implies when this tool is appropriate, but the description does not explicitly say when to use it over get_stock_quote_tool or mention any exclusions. Usage context is implied rather than stated.

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

Deploy Server