findata-mcp-server

getHistoricalData

Retrieve historical stock data for a symbol. Specify interval and output size to get daily, weekly, or monthly prices.

Instructions

Get historical data for a stock.

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>"
    },
    "name": "getHistoricalData"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes	The stock symbol (e.g., AAPL)
`interval`	No	The time interval for the data (daily, weekly, or monthly)	daily
`outputsize`	No	The size of the output (compact or full)	compact

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Jul 4, 2026

TDQS

C2.9/5.0

Behavior2/5

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states 'Get historical data' without mentioning rate limits, output format, data granularity, or any other behavioral traits, leaving significant gaps for a data-retrieval tool.

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 a single concise sentence that is easy to parse and front-loaded. While it is minimal, it avoids redundancy and clearly names the primary action and resource, though it could benefit from slightly more detail.

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?

Given the lack of annotations and output schema, the description is incomplete. It does not explain the return format, data types, or any caveats around intervals or output size. A more complete description would clarify what 'historical data' entails and what the response contains.

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 input schema fully covers all three parameters (symbol, interval, outputsize) with descriptions, so the baseline is 3. The tool description adds no additional parameter context beyond the schema, but it doesn't need to since the schema is self-explanatory.

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: retrieve historical data for a stock. While it doesn't explicitly distinguish from the sibling tool getStockQuote, the word 'historical' implies a contrast with current quote data, making the purpose understandable.

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 gives no guidance on when to use this tool versus alternatives like getStockQuote. It does not mention typical use cases, prerequisites, or exclusions, so the agent must infer usage solely from the name and input schema.

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

Deploy Server