Finance Toolkit

Overview Schema Source Related Servers Discussions Admin

market_data

Read-onlyIdempotent

Fetch raw financial data like historical prices, financial statements, and quotes for given tickers. For pre-computed ratios or metrics, use dedicated tools.

Instructions

Raw financial data (historical prices, income statement, balance sheet, cash flow statement, company profile, quotes, analyst estimates, dividend/earnings calendars, statistics, market risk premium by country, CFTC Commitment of Traders report). Use this ONLY for raw data needs — for pre-computed ratios, performance, risk, or model metrics use the dedicated tools instead. Requires tickers='AAPL' — use comma-separated values for multiple tickers. get_market_risk_premium and get_commitment_of_traders are ticker/country-agnostic snapshots and ignore most other parameters.

Available indicators: get_analyst_estimates, get_balance_sheet_statement, get_cash_flow_statement, get_commitment_of_traders, get_dividend_calendar, get_earnings_calendar, get_historical_data, get_historical_statistics, get_income_statement, get_intraday_data, get_market_risk_premium, get_profile, get_quote, get_rating, get_revenue_geographic_segmentation, get_revenue_product_segmentation, get_statistics_statement, get_treasury_data.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lag`	No	Number of periods to lag when computing growth rates.
`growth`	No	Return period-over-period growth rates instead of absolute values.
`period`	No	Observation frequency, e.g. 'monthly', 'quarterly', or 'annual'. Leave unset to use the default of the indicator you selected. Defaults are 'daily' for get_historical_data, get_treasury_data; '1hour' for get_intraday_data.
`tickers`	No	Comma-separated ticker symbols, e.g. 'AAPL,MSFT,GOOGL'.
`end_date`	No	End of the date range in YYYY-MM-DD format.	2026-10-02
`fill_nan`	No	Value for fill_nan.
`trailing`	No	Trailing window size in number of periods. Sums the raw values over the trailing N periods (e.g. trailing=4 on quarterly data gives a trailing-4-quarter / TTM-style sum) instead of returning one value per period.
`indicator`	Yes	Name of the specific metric to calculate, e.g. 'get_asset_turnover_ratio'. Required — omitting it returns the list of available indicators.
`quarterly`	No	Return quarterly data instead of annual when True.
`start_date`	No	Start of the date range in YYYY-MM-DD format.	2021-10-03
`show_errors`	No	Value for show_errors.
`actual_dates`	No	Value for actual_dates.
`show_columns`	No	Comma-separated names to filter the output. For historical data use the key names visible in any response record (e.g. 'Close,Volume,Return'). For financial statements use the 'metric' field values from the response (e.g. 'Revenue,Net Income,EBITDA'). Call the tool once without this parameter to see all available names, then repeat with show_columns to reduce response size and token usage.
`return_column`	No	Value for return_column. Leave unset to use the default of the indicator you selected. Defaults are 'Adj Close' for get_historical_data; 'Close' for get_intraday_data.
`divide_ohlc_by`	No	Value for divide_ohlc_by.
`enforce_source`	No	Value for enforce_source.
`risk_free_rate`	No	Value for risk_free_rate.
`benchmark_ticker`	No	Ticker used as the market benchmark, e.g. 'SPY' or '^GSPC'.	SPY
`include_dividends`	No	Value for include_dividends.
`show_ticker_seperation`	No	Value for show_ticker_seperation.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.2.1Oct 2, 2026
- changedInput schema / properties / end_date / default
```
Previous value: -"2026-08-19"New value: +"2026-10-02"
```
- changedInput schema / properties / start_date / default
```
Previous value: -"2021-08-20"New value: +"2021-10-03"
```

Changed11 schema fields changedv2.2.0Aug 19, 2026

changedInput schema / properties / end_date / default

Previous value: -"2026-07-14"New value: +"2026-08-19"

changedInput schema / properties / indicator / enum

Previous value: -[
-  "get_analyst_estimates",
-  "get_balance_sheet_statement",
-  "get_cash_flow_statement",
-  "get_dividend_calendar",
-  "get_earnings_calendar",
-  "get_historical_data",
-  "get_historical_statistics",
-  "get_income_statement",
-  "get_intraday_data",
-  "get_profile",
-  "get_quote",
-  "get_rating",
-  "get_revenue_geographic_segmentation",
-  "get_revenue_product_segmentation",
-  "get_statistics_statement",
-  "get_treasury_data"
-]New value: +[
+  "get_analyst_estimates",
+  "get_balance_sheet_statement",
+  "get_cash_flow_statement",
+  "get_commitment_of_traders",
+  "get_dividend_calendar",
+  "get_earnings_calendar",
+  "get_historical_data",
+  "get_historical_statistics",
+  "get_income_statement",
+  "get_intraday_data",
+  "get_market_risk_premium",
+  "get_profile",
+  "get_quote",
+  "get_rating",
+  "get_revenue_geographic_segmentation",
+  "get_revenue_product_segmentation",
+  "get_statistics_statement",
+  "get_treasury_data"
+]

addedInput schema / properties / period / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / period / default
```
Previous value: -"daily"New value: +null
```

changedInput schema / properties / period / description

Previous value: -"Observation frequency, e.g. 'monthly', 'quarterly', or 'annual'."New value: +"Observation frequency, e.g. 'monthly', 'quarterly', or 'annual'. Leave unset to use the default of the indicator you selected. Defaults are 'daily' for get_historical_data, get_treasury_data; '1hour' for get_intraday_data."

removedInput schema / properties / period / type
```
Removed value: -"string"
```

addedInput schema / properties / return_column / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / return_column / default
```
Previous value: -"Adj Close"New value: +null
```

changedInput schema / properties / return_column / description

Previous value: -"Value for return_column."New value: +"Value for return_column. Leave unset to use the default of the indicator you selected. Defaults are 'Adj Close' for get_historical_data; 'Close' for get_intraday_data."

removedInput schema / properties / return_column / type
```
Removed value: -"string"
```

changedInput schema / properties / start_date / default

Previous value: -"2021-07-15"New value: +"2021-08-20"

Changed3 schema fields changedJul 14, 2026

changedInput schema / properties / end_date / default

Previous value: -"2026-07-09"New value: +"2026-07-14"

changedInput schema / properties / start_date / default

Previous value: -"2021-07-10"New value: +"2021-07-15"

changedInput schema / properties / trailing / description

Previous value: -"Number of trailing periods for rolling-window calculations."New value: +"Trailing window size in number of periods. Sums the raw values over the trailing N periods (e.g. trailing=4 on quarterly data gives a trailing-4-quarter / TTM-style sum) instead of returning one value per period."

Changed2 schema fields changedv2.1.4Jul 9, 2026
- changedInput schema / properties / end_date / default
```
Previous value: -"2026-06-27"New value: +"2026-07-09"
```
- changedInput schema / properties / start_date / default
```
Previous value: -"2021-06-28"New value: +"2021-07-10"
```
Changed2 schema fields changedv2.1.3Jun 27, 2026
- changedInput schema / properties / end_date / default
```
Previous value: -"2026-06-23"New value: +"2026-06-27"
```
- changedInput schema / properties / start_date / default
```
Previous value: -"2021-06-24"New value: +"2021-06-28"
```

Changed4 schema fields changedv0.1.2Jun 23, 2026

changedInput schema / properties / end_date / default

Previous value: -"2026-06-22"New value: +"2026-06-23"

removedInput schema / properties / rounding

Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Number of decimal places to round results to.",
-  "title": "Rounding"
-}

addedInput schema / properties / show_columns

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Comma-separated names to filter the output. For historical data use the key names visible in any response record (e.g. 'Close,Volume,Return'). For financial statements use the 'metric' field values from the response (e.g. 'Revenue,Net Income,EBITDA'). Call the tool once without this parameter to see all available names, then repeat with show_columns to reduce response size and token usage.",
+  "title": "Show Columns"
+}

changedInput schema / properties / start_date / default

Previous value: -"2021-06-23"New value: +"2021-06-24"

Changed2 schema fields changedv0.1.1Jun 22, 2026
- changedInput schema / properties / end_date / default
```
Previous value: -"2026-06-21"New value: +"2026-06-22"
```
- changedInput schema / properties / start_date / default
```
Previous value: -"2021-06-22"New value: +"2021-06-23"
```
First observedv0.1.0Jun 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds genuinely non-obvious behavior: the ticker requirement and the fact that two indicators are ticker/country-agnostic snapshots that silently ignore most other parameters. It does not discuss rate limits or response size limits beyond the show_columns tip.

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?

Purpose and routing rule are front-loaded in the first two sentences, and the special-case note follows. The trailing 'Available indicators' list duplicates the enum already in the schema verbatim, which is wasted length, though it does aid quick scanning.

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?

For a 20-parameter aggregator with an output schema, the description covers routing, prerequisites, and the notable indicator quirks. The gaps are the opaque placeholder parameters, which neither the description nor the schema explains, but the presence of an output schema means return values need not be described here.

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?

Schema description coverage is 100%, so the per-parameter baseline is 3. The description adds cross-parameter semantics the schema does not: the required tickers format, the conditional irrelevance of parameters for two indicators, and the show_columns workflow for reducing token usage. It does not clarify the many placeholder parameters (fill_nan, show_errors, enforce_source, divide_ohlc_by), which remain 'Value for X' in the schema.

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 names a concrete resource (raw financial data) and enumerates the data families it covers (prices, statements, profile, quotes, calendars, COT report). It explicitly distinguishes itself from the sibling family of computed-metric tools ('for pre-computed ratios, performance, risk, or model metrics use the dedicated tools instead'), so an agent can route without opening the schema.

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

Usage Guidelines5/5

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

It gives an explicit when-to-use ('ONLY for raw data needs') and a when-not with the alternative class of tools to use instead. It also states the hard prerequisite (tickers='AAPL', comma-separated) and the edge case that get_market_risk_premium and get_commitment_of_traders ignore most other parameters.

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

market_data

Instructions

Input Schema

Output Schema

Schema Changelog

TDQS

Other Tools