Skip to main content
Glama

Fintel Discovery — Financial Intelligence for AI Agents

by io.github.findimitrov
OverviewDiscussionsAdmin

Get Price History — Multiple Tickers

GetMultiTickerHistory
Read-onlyIdempotent
    Fetch OHLCV price history for multiple tickers in a single call.
    Returns a flattened table with columns like 'AAPL_Close', 'SPY_Volume', etc.

    Use this tool when:
    - You are comparing performance across multiple securities
    - You need correlated price data for a portfolio or basket of tickers
    - You want to compute relative performance or correlation matrices

    Pass symbols as a space-separated or comma-separated string:
    'AAPL MSFT GOOGL' or 'SPY,QQQ,IWM'.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $defs / MultiTickerHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"5f4db44b-e5cc-4f3a-8da3-ac591a019c81"New value: +"f258bd16-f060-4e4a-a55d-221a0484866d"
  2. Changed1 schema field changed
    • changedInput schema / $defs / MultiTickerHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"d9f77642-e017-4785-9150-e658c2dba3a0"New value: +"5f4db44b-e5cc-4f3a-8da3-ac591a019c81"
  3. Changed1 schema field changed
    • changedInput schema / $defs / MultiTickerHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"dbe99169-c071-4ed4-9ae9-8bbfb9a88ad8"New value: +"d9f77642-e017-4785-9150-e658c2dba3a0"
  4. Changed1 schema field changed
    • changedInput schema / $defs / MultiTickerHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"3775b46a-5aa8-4586-af57-2453c8bcd08c"New value: +"dbe99169-c071-4ed4-9ae9-8bbfb9a88ad8"
  5. Changed1 schema field changed
    • changedInput schema / $defs / MultiTickerHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"d81a5175-11e9-494a-baa5-71d4ffad4ab9"New value: +"3775b46a-5aa8-4586-af57-2453c8bcd08c"
  6. Changed1 schema field changed
    • changedInput schema / $defs / MultiTickerHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"9e7f8798-7d22-4378-b93d-179c6f8cb854"New value: +"d81a5175-11e9-494a-baa5-71d4ffad4ab9"
  7. Changed1 schema field changed
    • changedInput schema / $defs / MultiTickerHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"9919ff85-e960-472f-863b-3de4c5abed9f"New value: +"9e7f8798-7d22-4378-b93d-179c6f8cb854"
  8. Changed1 schema field changed
    • changedInput schema / $defs / MultiTickerHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"38452924-d5df-4668-b51c-d7cd5acabc09"New value: +"9919ff85-e960-472f-863b-3de4c5abed9f"
  9. Changed1 schema field changed
    • changedInput schema / $defs / MultiTickerHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"fa72f604-6239-428b-81df-11f07c2c8d00"New value: +"38452924-d5df-4668-b51c-d7cd5acabc09"
  10. Changed1 schema field changed
    • changedInput schema / $defs / MultiTickerHistoryParams / properties / mcp_prompt_id / default
      Previous value: -"7b866f24-13ab-4e54-8d3a-f775612c393f"New value: +"fa72f604-6239-428b-81df-11f07c2c8d00"
  11. 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=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context beyond those: it returns a flattened table, accepts multiple symbol formats, and identifies the data source as Yahoo Finance via yfinance with no API key required.

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 well-structured and front-loaded: a crisp one-sentence summary, clear use-case bullets, a concrete symbols example, and a source note. Every sentence adds value without unnecessary repetition.

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 annotations and output schema, the description covers the essential invocation details: purpose, symbol format, returned data shape, and data source. It could be more complete by explicitly steering single-ticker requests to GetPriceHistory, but it is still adequate for correct multi-ticker usage.

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 the symbols parameter format and hints at OHLCV output, but the schema's parameter descriptions already cover symbols, dates, period, and interval. The nested schema contains many unrelated parameters (e.g., wholesaler_ids, exclude_fillers) that the description does not clarify or warn against, which could confuse an agent.

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 states a specific verb and resource: 'Fetch OHLCV price history for multiple tickers in a single call.' It also clarifies the output shape with example columns like 'AAPL_Close' and 'SPY_Volume', which helps distinguish it from single-ticker tools like GetPriceHistory.

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 description explicitly lists use cases: comparing multiple securities, correlated price data, and correlation matrices. It does not explicitly mention when not to use it or name the single-ticker alternative, but the context is clear enough for an agent to choose this tool for multi-ticker needs.

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 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources