Finance Toolkit

Overview Schema Source Related Servers Discussions Admin

momentum

Read-onlyIdempotent

Calculate technical indicators like RSI, MACD, and Stochastic from ticker symbols. Automatically uses price data without requiring a separate price fetch.

Instructions

Momentum technical indicators (RSI, MACD, Stochastic Oscillator, Williams %R, Aroon). Applied to price data automatically — no need to fetch prices first. Requires tickers='AAPL' — use comma-separated values for multiple tickers.

Available indicators: get_money_flow_index, get_williams_percent_r, get_aroon_indicator, get_commodity_channel_index, get_relative_vigor_index, get_force_index, get_ultimate_oscillator, get_percentage_price_oscillator, get_detrended_price_oscillator, get_average_directional_index, get_chande_momentum_oscillator, get_ichimoku_cloud, get_stochastic_oscillator, get_moving_average_convergence_divergence, get_relative_strength_index, get_balance_of_power, get_awesome_oscillator, get_vortex_indicator, get_elder_ray_index, get_rate_of_change, get_choppiness_index, get_know_sure_thing.

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'.	daily
`window`	No	Value for window. Leave unset to use the default of the indicator you selected. Defaults differ between indicators.
`tickers`	No	Comma-separated ticker symbols, e.g. 'AAPL,MSFT,GOOGL'.
`weights`	No	Value for weights.
`constant`	No	Value for constant.
`end_date`	No	End of the date range in YYYY-MM-DD format.	2026-10-02
`window_1`	No	Value for window_1.
`window_2`	No	Value for window_2.
`window_3`	No	Value for window_3.
`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
`base_window`	No	Value for base_window.
`long_window`	No	Value for long_window. Leave unset to use the default of the indicator you selected. Defaults are 26 for get_moving_average_convergence_divergence; 28 for get_percentage_price_oscillator; 34 for get_awesome_oscillator.
`roc_windows`	No	Value for roc_windows.
`sma_windows`	No	Value for sma_windows.
`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.
`close_column`	No	Value for close_column.	Adj Close
`short_window`	No	Value for short_window. Leave unset to use the default of the indicator you selected. Defaults are 12 for get_moving_average_convergence_divergence; 5 for get_awesome_oscillator; 7 for get_percentage_price_oscillator.
`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.
`signal_window`	No	Value for signal_window.
`smooth_window`	No	Value for smooth_window.
`benchmark_ticker`	No	Ticker used as the market benchmark, e.g. 'SPY' or '^GSPC'.	SPY
`conversion_window`	No	Value for conversion_window.
`lead_span_b_window`	No	Value for lead_span_b_window.

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 / base_window / default
```
Previous value: -20New value: +26
```

changedInput schema / properties / end_date / default

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

changedInput schema / properties / indicator / enum

Previous value: -[
-  "get_money_flow_index",
-  "get_williams_percent_r",
-  "get_aroon_indicator",
-  "get_commodity_channel_index",
-  "get_relative_vigor_index",
-  "get_force_index",
-  "get_ultimate_oscillator",
-  "get_percentage_price_oscillator",
-  "get_detrended_price_oscillator",
-  "get_average_directional_index",
-  "get_chande_momentum_oscillator",
-  "get_ichimoku_cloud",
-  "get_stochastic_oscillator",
-  "get_moving_average_convergence_divergence",
-  "get_relative_strength_index",
-  "get_balance_of_power"
-]New value: +[
+  "get_money_flow_index",
+  "get_williams_percent_r",
+  "get_aroon_indicator",
+  "get_commodity_channel_index",
+  "get_relative_vigor_index",
+  "get_force_index",
+  "get_ultimate_oscillator",
+  "get_percentage_price_oscillator",
+  "get_detrended_price_oscillator",
+  "get_average_directional_index",
+  "get_chande_momentum_oscillator",
+  "get_ichimoku_cloud",
+  "get_stochastic_oscillator",
+  "get_moving_average_convergence_divergence",
+  "get_relative_strength_index",
+  "get_balance_of_power",
+  "get_awesome_oscillator",
+  "get_vortex_indicator",
+  "get_elder_ray_index",
+  "get_rate_of_change",
+  "get_choppiness_index",
+  "get_know_sure_thing"
+]

changedInput schema / properties / lead_span_b_window / default
```
Previous value: -40New value: +52
```

addedInput schema / properties / long_window / anyOf

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

changedInput schema / properties / long_window / default
```
Previous value: -28New value: +null
```

changedInput schema / properties / long_window / description

Previous value: -"Value for long_window."New value: +"Value for long_window. Leave unset to use the default of the indicator you selected. Defaults are 26 for get_moving_average_convergence_divergence; 28 for get_percentage_price_oscillator; 34 for get_awesome_oscillator."

removedInput schema / properties / long_window / type
```
Removed value: -"integer"
```

addedInput schema / properties / roc_windows

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Value for roc_windows.",
+  "title": "Roc Windows"
+}

addedInput schema / properties / short_window / anyOf

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

changedInput schema / properties / short_window / default
```
Previous value: -7New value: +null
```

changedInput schema / properties / short_window / description

Previous value: -"Value for short_window."New value: +"Value for short_window. Leave unset to use the default of the indicator you selected. Defaults are 12 for get_moving_average_convergence_divergence; 5 for get_awesome_oscillator; 7 for get_percentage_price_oscillator."

removedInput schema / properties / short_window / type
```
Removed value: -"integer"
```

addedInput schema / properties / sma_windows

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Value for sma_windows.",
+  "title": "Sma Windows"
+}

removedInput schema / properties / smooth_widow

Removed value: -{
-  "default": 3,
-  "description": "Value for smooth_widow.",
-  "title": "Smooth Widow",
-  "type": "integer"
-}

addedInput schema / properties / smooth_window

Added value: +{
+  "default": 3,
+  "description": "Value for smooth_window.",
+  "title": "Smooth Window",
+  "type": "integer"
+}

changedInput schema / properties / start_date / default

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

addedInput schema / properties / weights

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Value for weights.",
+  "title": "Weights"
+}

addedInput schema / properties / window / anyOf

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

changedInput schema / properties / window / default
```
Previous value: -14New value: +null
```

changedInput schema / properties / window / description

Previous value: -"Value for window."New value: +"Value for window. Leave unset to use the default of the indicator you selected. Defaults differ between indicators."

removedInput schema / properties / window / type
```
Removed value: -"integer"
```

Changed3 schema fields changedJul 14, 2026

changedInput schema / properties / end_date / default

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

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"

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 safety is covered. The description usefully adds that price data is applied automatically and that tickers/indicator are the driving inputs, but says nothing about output shape, latency, rate limits, or what the many window parameters do per indicator.

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 two sentences are well front-loaded and earn their place. The trailing list of 22 indicator names duplicates the enum already present in the schema verbatim, adding bulk without new 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?

For a 27-parameter tool with a full output schema, the description covers the essential contract (indicator selection plus tickers) but leaves the interaction between indicator choice and the numerous window parameters entirely to the schema. It is adequate but does not reduce the trial-and-error of configuring per-indicator windows.

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 the schema already documents all 27 parameters, and the description is not obliged to compensate. It reinforces only the tickers and indicator parameters, adding the comma-separated multi-ticker convention, which is marginally helpful but below the schema's own detail level.

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 first sentence names a specific resource ('momentum technical indicators') and enumerates the families (RSI, MACD, Stochastic, Williams %R, Aroon), so an agent knows it is the technical-indicator calculator rather than a raw price fetcher. It stops short of distinguishing itself from siblings like volatility or market_data, which also deal with price series.

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?

It gives concrete invocation guidance ('Requires tickers="AAPL"', comma-separated for multiples) and notes that prices are fetched automatically. It never says when to prefer this over volatility, models, or market_data, nor when-not to use it, so selection guidance is only implied.

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

momentum

Instructions

Input Schema

Output Schema

Schema Changelog

TDQS

Other Tools