Skip to main content
Glama
financial-datasets

Financial Datasets MCP Server

Official

get_historical_stock_prices

Retrieve historical stock price data for analysis by specifying ticker symbol, date range, and interval parameters.

Instructions

Gets historical stock prices for a company.

Args:
    ticker: Ticker symbol of the company (e.g. AAPL, GOOGL)
    start_date: Start date of the price data (e.g. 2020-01-01)
    end_date: End date of the price data (e.g. 2020-12-31)
    interval: Interval of the price data (e.g. minute, hour, day, week, month)
    interval_multiplier: Multiplier of the interval (e.g. 1, 2, 3)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYes
start_dateYes
end_dateYes
intervalNoday
interval_multiplierNo

Implementation Reference

  • Handler function decorated with @mcp.tool() that implements the get_historical_stock_prices tool. It fetches historical stock prices via the Financial Datasets API using the make_request helper, processes the response, and returns JSON-formatted prices.
    @mcp.tool()
    async def get_historical_stock_prices(
        ticker: str,
        start_date: str,
        end_date: str,
        interval: str = "day",
        interval_multiplier: int = 1,
    ) -> str:
        """Gets historical stock prices for a company.
    
        Args:
            ticker: Ticker symbol of the company (e.g. AAPL, GOOGL)
            start_date: Start date of the price data (e.g. 2020-01-01)
            end_date: End date of the price data (e.g. 2020-12-31)
            interval: Interval of the price data (e.g. minute, hour, day, week, month)
            interval_multiplier: Multiplier of the interval (e.g. 1, 2, 3)
        """
        # Fetch data from the API
        url = f"{FINANCIAL_DATASETS_API_BASE}/prices/?ticker={ticker}&interval={interval}&interval_multiplier={interval_multiplier}&start_date={start_date}&end_date={end_date}"
        data = await make_request(url)
    
        # Check if data is found
        if not data:
            return "Unable to fetch prices or no prices found."
    
        # Extract the prices
        prices = data.get("prices", [])
    
        # Check if prices are found
        if not prices:
            return "Unable to fetch prices or no prices found."
    
        # Stringify the prices
        return json.dumps(prices, indent=2)
  • Helper function used by get_historical_stock_prices to make authenticated HTTP requests to the Financial Datasets API.
    async def make_request(url: str) -> dict[str, any] | None:
        """Make a request to the Financial Datasets API with proper error handling."""
        # Load environment variables from .env file
        load_dotenv()
        
        headers = {}
        if api_key := os.environ.get("FINANCIAL_DATASETS_API_KEY"):
            headers["X-API-KEY"] = api_key
    
        async with httpx.AsyncClient() as client:
            try:
                response = await client.get(url, headers=headers, timeout=30.0)
                response.raise_for_status()
                return response.json()
            except Exception as e:
                return {"Error": str(e)}
  • server.py:165-165 (registration)
    MCP tool registration decorator for the get_historical_stock_prices handler.
    @mcp.tool()
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only describes what the tool does ('Gets historical stock prices') without mentioning rate limits, authentication requirements, data source, response format, error conditions, or whether this is a read-only operation. For a data retrieval tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 perfectly structured and concise. It starts with a clear purpose statement, then provides a well-organized parameter section with each parameter explained in a single line with helpful examples. Every sentence earns its place with no redundant information.

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 5 parameters, no annotations, and no output schema, the description does an adequate job on parameters but lacks critical context. It explains what parameters to provide but doesn't describe what the tool returns (data format, structure), error handling, or behavioral constraints. For a data retrieval tool with multiple parameters, this leaves the agent with incomplete understanding of the full operation.

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

Parameters4/5

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

The description provides excellent parameter semantics despite 0% schema description coverage. It clearly explains each parameter's purpose with examples: ticker symbol examples (AAPL, GOOGL), date format examples (2020-01-01), interval options (minute, hour, day, week, month), and interval_multiplier examples (1, 2, 3). This fully compensates for the lack of schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 'Gets historical stock prices for a company' - a specific verb ('Gets') and resource ('historical stock prices'). It distinguishes from siblings like get_current_stock_price by specifying historical data, but doesn't explicitly differentiate from get_historical_crypto_prices beyond the 'stock' vs 'crypto' distinction in names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose this over get_current_stock_price for real-time data, or how it relates to get_historical_crypto_prices for different asset classes. No prerequisites, limitations, or comparison context is 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/financial-datasets/mcp-server'

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