Financial Modeling Prep (FMP) MCP Server

get_historical_chart

Retrieve historical stock price data with customizable time intervals to analyze market trends and performance over specific periods.

Instructions

Get historical price data with flexible time intervals

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": {
      "symbol": "<symbol>",
      "interval": "<interval>"
    },
    "name": "get_historical_chart"
  }
}

Input Schema

Name	Required	Description
`symbol`	Yes	Stock ticker symbol
`interval`	Yes	Time interval
`from`	No	Start date in YYYY-MM-DD format (optional)
`to`	No	End date in YYYY-MM-DD format (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Mar 17, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral insight. It mentions 'flexible time intervals' but doesn't disclose rate limits, authentication needs, data freshness, or output format. This leaves significant gaps for a tool that likely involves external data fetching.

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, efficient sentence with no wasted words. It's front-loaded with the core purpose ('Get historical price data') and adds a useful qualifier ('with flexible time intervals'). Every part earns its place.

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

Completeness2/5

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

For a tool with 4 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what the output contains (e.g., price points, timestamps), error conditions, or behavioral constraints, leaving the agent with insufficient context for reliable use.

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%, so parameters are well-documented in the schema. The description adds little beyond implying time-based filtering, but doesn't explain parameter interactions or default behaviors (e.g., what happens if 'from'/'to' are omitted). Baseline 3 is appropriate as the schema does the heavy lifting.

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 action ('Get historical price data') and resource ('price data'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_quote' or 'get_technical_indicator_*' which might also provide price-related data, missing explicit distinction.

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?

No guidance is provided on when to use this tool versus alternatives. The description mentions 'flexible time intervals' but doesn't specify use cases, prerequisites, or exclusions compared to siblings like 'get_quote' for current prices or technical indicators for derived metrics.

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