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

TableJSON Schema

Name	Required	Description	Default
`params`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already communicate read-only/idempotent/non-destructive behavior. The description adds useful context beyond annotations by naming Yahoo Finance via yfinance as the source, stating no API key is required, and documenting intraday max lookback limits (730 days for 1h, 60 days for shorter intraday bars).

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 compact, front-loaded with the core purpose, and uses short bullets and option lists. Every sentence adds useful information, and it avoids restating unrelated schema details.

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 exists and annotations cover safety, the description provides enough context about source, interval limits, and use cases. It could be slightly stronger by explicitly routing multi-ticker requests to GetMultiTickerHistory, but nothing critical is missing for standard single-ticker history calls.

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 summarizes interval and period options and adds max-day constraints, which is helpful. However, the input schema already documents these values, and the description does not cover important parameters such as start/end precedence, actions, auto_adjust, or source_resource_id, so it only partially compensates for the low schema coverage signal.

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 ('Fetch') and names the exact resource: OHLCV price history for one ticker. It also distinguishes this tool from sibling tools like GetMultiTickerHistory by explicitly narrowing scope to a single ticker.

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?

The 'Use this tool when' section gives clear, concrete scenarios such as analyzing performance over a time range and computing returns/volatility/trends. It does not explicitly name an alternative tool to use for multi-ticker history, so it stops short of full when-not guidance.

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

All Fintel Discovery — Financial Intelligence for AI Agents tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Most tools target a distinct resource and action, with clear separation between search and detail tools (e.g., SearchIAPDFirm vs GetIAPDFirmDetail, SearchBrokerCheck vs GetBrokerCheckDetail). A few pairs like SearchBrokerCheck and SearchBrokerCheckFirm could cause momentary confusion, but descriptions clarify individual vs firm scope.

Naming Consistency4/5

The dominant pattern is consistent: Search* for discovery, Get* for retrieval, with CamelCase throughout. Minor deviations like LookupTicker and MapInstrumentIds introduce different verbs, and SearchBrokerCheck does not explicitly signal 'individual' unlike SearchBrokerCheckFirm, but the overall convention remains predictable.

Tool Count2/5

With 32 tools, the surface is quite heavy and exceeds the 25+ threshold for 'too many.' While the financial intelligence domain is broad, several search/detail pairs and overlapping data-source tools could be consolidated to reduce cognitive load for agents.

Completeness4/5

The toolset covers major workflows well: 13F holdings, fund fee comparison, advisor due diligence, macro data, price history, options, and identifier mapping. Minor gaps exist, such as no standalone real-time quote tool, no news/sentiment data, and no direct CUSIP-to-company-name search, but these are workable around.

Resources

Need Help?