Skip to main content
Glama
NARAVINDR321

Financial Analysis MCP Server

by NARAVINDR321

retrieve_stock_data

Retrieve historical stock data for specified tickers, date range, and interval using yfinance. Outputs a dictionary mapping tickers to their historical data for analysis and research.

Instructions

Retrieves stock data for a list of tickers using yfinance.
Args:
    ticker_list: List of ticker symbols (e.g., ['AAPL', 'MSFT', 'GOOGL'])
    start_date: Start date of the data (e.g., '2024-01-01')
    end_date: End date of the data (e.g., '2024-12-31')
    interval: Data interval (e.g., '1d', '1h', '5m', etc.)
Returns:
    Dict mapping ticker to its historical data (as a list of dicts).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_dateYes
intervalNo1d
start_dateYes
ticker_listYes
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. It mentions the tool retrieves data using yfinance but lacks details on behavioral traits such as rate limits, error handling, authentication needs, or data freshness. The description does not contradict annotations, but it is insufficient for a mutation-free tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded with the core purpose, followed by structured parameter and return sections. Every sentence adds value, though it could be slightly more concise by integrating examples inline.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and 4 parameters, the description covers input semantics well but lacks behavioral context (e.g., rate limits, errors) and detailed output explanation. It is adequate for basic use but has clear gaps for robust agent interaction.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by explaining all four parameters with clear semantics, examples, and the return structure. It adds significant meaning beyond the basic schema, detailing ticker_list as a list of symbols, date formats, interval options, and the output mapping.

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 clearly states the tool's purpose with a specific verb ('Retrieves') and resource ('stock data for a list of tickers using yfinance'), distinguishing it from siblings like retrieve_current_price or retrieve_financial_statements by specifying historical data retrieval.

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 description implies usage for historical stock data retrieval but does not explicitly state when to use this tool versus alternatives like retrieve_current_price (for real-time data) or other siblings. No exclusions or specific contexts are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NARAVINDR321/MCP_Server_for_Financial_Analysis'

If you have feedback or need assistance with the MCP directory API, please join our Discord server