Finance Toolkit

Overview Schema Source Related Servers Discussions Admin

models

Read-onlyIdempotent

Calculate valuation, profitability, risk, and growth indicators—such as WACC, DCF, DuPont, and bankruptcy scores—directly from stock fundamental data.

Instructions

Pre-computed financial models (WACC, DuPont analysis, Extended DuPont analysis, Enterprise value breakdown, intrinsic value/DCF, Gordon Growth Model, Altman Z-Score, Piotroski F-Score, Beneish M-Score, Economic Value Added (EVA), Present Value of Growth Opportunities, Sustainable Growth Rate, Internal Growth Rate, Graham Number). Requires tickers='AAPL' — use comma-separated values for multiple tickers. Supports quarterly=true and start_date/end_date.

Available indicators: get_altman_z_score, get_beneish_m_score, get_dupont_analysis, get_economic_value_added, get_enterprise_value_breakdown, get_extended_dupont_analysis, get_free_cash_flow_to_equity, get_free_cash_flow_to_firm, get_fulmer_h_score, get_gorden_growth_model, get_graham_number, get_grover_score, get_internal_growth_rate, get_intrinsic_valuation, get_market_value_added, get_ohlson_o_score, get_piotroski_score, get_present_value_of_growth_opportunities, get_residual_income, get_springate_score, get_sustainable_growth_rate, get_tobins_q_ratio, get_two_stage_dividend_discount_model, get_weighted_average_cost_of_capital, get_zmijewski_score.

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.
`diluted`	No	Value for diluted.
`periods`	No	Value for periods.
`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
`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
`growth_rate`	No	Assumed constant growth rate as a decimal. Leave unset to use the default of the indicator you selected. Required by: get_gorden_growth_model, get_intrinsic_valuation.
`standardize`	No	Return the Z-Score (standard score) instead of the raw values, i.e. how many standard deviations each value is from the mean of its own series. When combined with growth=True, the growth values are standardized instead of the raw values.
`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.
`cash_flow_type`	No	Value for cash_flow_type.	Free Cash Flow
`rate_of_return`	No	Value for rate_of_return. Leave unset to use the default of the indicator you selected. Required by: get_gorden_growth_model, get_two_stage_dividend_discount_model.
`calculate_daily`	No	Value for calculate_daily.
`project_periods`	No	Value for project_periods.
`benchmark_ticker`	No	Ticker used as the market benchmark, e.g. 'SPY' or '^GSPC'.	SPY
`high_growth_rate`	No	Value for high_growth_rate. Leave unset to use the default of the indicator you selected. Required by: get_two_stage_dividend_discount_model.
`include_dividends`	No	Value for include_dividends.
`show_full_results`	No	Value for show_full_results.
`stable_growth_rate`	No	Value for stable_growth_rate. Leave unset to use the default of the indicator you selected. Required by: get_two_stage_dividend_discount_model.
`high_growth_periods`	No	Value for high_growth_periods.
`perpetual_growth_rate`	No	Terminal (perpetual) growth rate used in DCF models. Leave unset to use the default of the indicator you selected. Required by: get_intrinsic_valuation.
`weighted_average_cost_of_capital`	No	WACC as a decimal, e.g. 0.09 for 9 %. Leave unset to use the default of the indicator you selected. Required by: get_intrinsic_valuation.

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"
```

Changed22 schema fields changedv2.2.0Aug 19, 2026

changedInput schema / properties / end_date / default

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

addedInput schema / properties / growth_rate / anyOf

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

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

changedInput schema / properties / growth_rate / description

Previous value: -"Assumed constant growth rate as a decimal."New value: +"Assumed constant growth rate as a decimal. Leave unset to use the default of the indicator you selected. Required by: get_gorden_growth_model, get_intrinsic_valuation."

removedInput schema / properties / growth_rate / type
```
Removed value: -"number"
```

addedInput schema / properties / high_growth_periods

Added value: +{
+  "default": 5,
+  "description": "Value for high_growth_periods.",
+  "title": "High Growth Periods",
+  "type": "integer"
+}

addedInput schema / properties / high_growth_rate

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Value for high_growth_rate. Leave unset to use the default of the indicator you selected. Required by: get_two_stage_dividend_discount_model.",
+  "title": "High Growth Rate"
+}

changedInput schema / properties / indicator / enum

Previous value: -[
-  "get_altman_z_score",
-  "get_beneish_m_score",
-  "get_dupont_analysis",
-  "get_economic_value_added",
-  "get_enterprise_value_breakdown",
-  "get_extended_dupont_analysis",
-  "get_gorden_growth_model",
-  "get_graham_number",
-  "get_internal_growth_rate",
-  "get_intrinsic_valuation",
-  "get_piotroski_score",
-  "get_present_value_of_growth_opportunities",
-  "get_sustainable_growth_rate",
-  "get_weighted_average_cost_of_capital"
-]New value: +[
+  "get_altman_z_score",
+  "get_beneish_m_score",
+  "get_dupont_analysis",
+  "get_economic_value_added",
+  "get_enterprise_value_breakdown",
+  "get_extended_dupont_analysis",
+  "get_free_cash_flow_to_equity",
+  "get_free_cash_flow_to_firm",
+  "get_fulmer_h_score",
+  "get_gorden_growth_model",
+  "get_graham_number",
+  "get_grover_score",
+  "get_internal_growth_rate",
+  "get_intrinsic_valuation",
+  "get_market_value_added",
+  "get_ohlson_o_score",
+  "get_piotroski_score",
+  "get_present_value_of_growth_opportunities",
+  "get_residual_income",
+  "get_springate_score",
+  "get_sustainable_growth_rate",
+  "get_tobins_q_ratio",
+  "get_two_stage_dividend_discount_model",
+  "get_weighted_average_cost_of_capital",
+  "get_zmijewski_score"
+]

addedInput schema / properties / perpetual_growth_rate / anyOf

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

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

changedInput schema / properties / perpetual_growth_rate / description

Previous value: -"Terminal (perpetual) growth rate used in DCF models."New value: +"Terminal (perpetual) growth rate used in DCF models. Leave unset to use the default of the indicator you selected. Required by: get_intrinsic_valuation."

removedInput schema / properties / perpetual_growth_rate / type
```
Removed value: -"number"
```

addedInput schema / properties / rate_of_return / anyOf

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

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

changedInput schema / properties / rate_of_return / description

Previous value: -"Value for rate_of_return."New value: +"Value for rate_of_return. Leave unset to use the default of the indicator you selected. Required by: get_gorden_growth_model, get_two_stage_dividend_discount_model."

removedInput schema / properties / rate_of_return / type
```
Removed value: -"number"
```

addedInput schema / properties / stable_growth_rate

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Value for stable_growth_rate. Leave unset to use the default of the indicator you selected. Required by: get_two_stage_dividend_discount_model.",
+  "title": "Stable Growth Rate"
+}

changedInput schema / properties / start_date / default

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

addedInput schema / properties / weighted_average_cost_of_capital / anyOf

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

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

changedInput schema / properties / weighted_average_cost_of_capital / description

Previous value: -"WACC as a decimal, e.g. 0.09 for 9 %."New value: +"WACC as a decimal, e.g. 0.09 for 9 %. Leave unset to use the default of the indicator you selected. Required by: get_intrinsic_valuation."

removedInput schema / properties / weighted_average_cost_of_capital / type
```
Removed value: -"number"
```

Changed5 schema fields changedJul 14, 2026

changedInput schema / properties / end_date / default

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

changedInput schema / properties / indicator / enum

Previous value: -[
-  "get_altman_z_score",
-  "get_dupont_analysis",
-  "get_enterprise_value_breakdown",
-  "get_extended_dupont_analysis",
-  "get_gorden_growth_model",
-  "get_intrinsic_valuation",
-  "get_piotroski_score",
-  "get_present_value_of_growth_opportunities",
-  "get_weighted_average_cost_of_capital"
-]New value: +[
+  "get_altman_z_score",
+  "get_beneish_m_score",
+  "get_dupont_analysis",
+  "get_economic_value_added",
+  "get_enterprise_value_breakdown",
+  "get_extended_dupont_analysis",
+  "get_gorden_growth_model",
+  "get_graham_number",
+  "get_internal_growth_rate",
+  "get_intrinsic_valuation",
+  "get_piotroski_score",
+  "get_present_value_of_growth_opportunities",
+  "get_sustainable_growth_rate",
+  "get_weighted_average_cost_of_capital"
+]

addedInput schema / properties / standardize

Added value: +{
+  "default": false,
+  "description": "Return the Z-Score (standard score) instead of the raw values, i.e. how many standard deviations each value is from the mean of its own series. When combined with growth=True, the growth values are standardized instead of the raw values.",
+  "title": "Standardize",
+  "type": "boolean"
+}

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"

Addedv0.1.1Jun 22, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered and the description only needs to add non-obvious behavior. It adds that resolution is per-indicator and that several inputs are optional, but not much beyond the schema. It also asserts 'Requires tickers=AAPL' while the schema marks only indicator as required, which is a mild inconsistency with structured data.

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

Conciseness3/5

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

The opening sentence is well front-loaded and the usage line is terse. The 'Available indicators:' block duplicates the indicator enum wholesale, which is pure token bloat in the tool description for a 25-param tool, though it does map human-readable model names to the enum values.

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?

An output schema exists so return values need no explanation, and annotations cover the safety profile. For a 25-parameter tool, however, the description only covers four inputs and leaves many vaguely documented parameters (periods, diluted, show_full_results, cash_flow_type) to the schema, and does not differentiate this tool from the valuation sibling.

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% and 1 of 25 parameters carries an enum, so the schema does the heavy lifting; baseline is 3. The description restates tickers/quarterly/start_date/end_date semantics that already exist verbatim in the schema and adds no new meaning for the many bare 'Value for X' parameters.

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?

Names a specific resource (pre-computed financial models) and enumerates the concrete metrics it produces (WACC, DuPont, DCF, Altman Z-Score, etc.), so an agent knows exactly what family of computations this covers. It does not, however, differentiate itself from siblings like valuation or profitability, which overlap with several of the listed indicators.

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?

Gives operational usage for the main inputs (tickers comma-separated, quarterly=true, start_date/end_date), which is real guidance for calling it. It never states when to prefer this tool over the valuation/solvency/profitability siblings, so the routing decision between overlapping tools is left to inference.

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

models

Instructions

Input Schema

Output Schema

Schema Changelog

TDQS

Other Tools