Skip to main content
Glama
JerBouma

Finance Toolkit

by JerBouma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

overlap

Read-onlyIdempotent

Calculate technical indicators such as SMA, EMA, Bollinger Bands, and Keltner Channels from ticker price data automatically; no separate price fetch needed.

Instructions

Overlap technical indicators (SMA, EMA, Bollinger Bands, Keltner Channels). Applied to price data automatically — no need to fetch prices first. Requires tickers='AAPL' — use comma-separated values for multiple tickers.

Available indicators: get_moving_average, get_exponential_moving_average, get_double_exponential_moving_average, get_trix, get_triangular_moving_average, get_weighted_moving_average, get_hull_moving_average, get_kaufman_adaptive_moving_average, get_volume_weighted_average_price, get_parabolic_sar, get_pivot_points, get_fibonacci_retracement_levels, get_support_resistance_levels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lagNoNumber of periods to lag when computing growth rates.
trendNoValue for trend.uptrend
af_maxNoValue for af_max.
growthNoReturn period-over-period growth rates instead of absolute values.
levelsNoValue for levels.
periodNoObservation frequency, e.g. 'monthly', 'quarterly', or 'annual'.daily
windowNoValue for window. Leave unset to use the default of the indicator you selected. Defaults differ between indicators.
tickersNoComma-separated ticker symbols, e.g. 'AAPL,MSFT,GOOGL'.
af_startNoValue for af_start.
end_dateNoEnd of the date range in YYYY-MM-DD format.2026-10-02
indicatorYesName of the specific metric to calculate, e.g. 'get_asset_turnover_ratio'. Required — omitting it returns the list of available indicators.
quarterlyNoReturn quarterly data instead of annual when True.
start_dateNoStart of the date range in YYYY-MM-DD format.2021-10-03
fast_windowNoValue for fast_window.
sensitivityNoValue for sensitivity.
slow_windowNoValue for slow_window.
standardizeNoReturn 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.
af_incrementNoValue for af_increment.
close_columnNoValue for close_column.Adj Close
show_columnsNoComma-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.
benchmark_tickerNoTicker used as the market benchmark, e.g. 'SPY' or '^GSPC'.SPY

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.2.1
    • 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"
  2. Changed12 schema fields changedv2.2.0
    • changedInput schema / properties / end_date / default
      Previous value: -"2026-07-14"New value: +"2026-08-19"
    • addedInput schema / properties / fast_window
      Added value: +{
+  "default": 2,
+  "description": "Value for fast_window.",
+  "title": "Fast Window",
+  "type": "integer"
+}
    • changedInput schema / properties / indicator / enum
      Previous value: -[
-  "get_moving_average",
-  "get_exponential_moving_average",
-  "get_double_exponential_moving_average",
-  "get_trix",
-  "get_triangular_moving_average",
-  "get_weighted_moving_average",
-  "get_hull_moving_average",
-  "get_volume_weighted_average_price",
-  "get_parabolic_sar",
-  "get_pivot_points"
-]New value: +[
+  "get_moving_average",
+  "get_exponential_moving_average",
+  "get_double_exponential_moving_average",
+  "get_trix",
+  "get_triangular_moving_average",
+  "get_weighted_moving_average",
+  "get_hull_moving_average",
+  "get_kaufman_adaptive_moving_average",
+  "get_volume_weighted_average_price",
+  "get_parabolic_sar",
+  "get_pivot_points",
+  "get_fibonacci_retracement_levels",
+  "get_support_resistance_levels"
+]
    • addedInput schema / properties / levels
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Value for levels.",
+  "title": "Levels"
+}
    • addedInput schema / properties / sensitivity
      Added value: +{
+  "default": 0.05,
+  "description": "Value for sensitivity.",
+  "title": "Sensitivity",
+  "type": "number"
+}
    • addedInput schema / properties / slow_window
      Added value: +{
+  "default": 30,
+  "description": "Value for slow_window.",
+  "title": "Slow Window",
+  "type": "integer"
+}
    • changedInput schema / properties / start_date / default
      Previous value: -"2021-07-15"New value: +"2021-08-20"
    • addedInput schema / properties / trend
      Added value: +{
+  "default": "uptrend",
+  "description": "Value for trend.",
+  "title": "Trend",
+  "type": "string"
+}
    • 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"
  3. Changed7 schema fields changed
    • addedInput schema / properties / af_increment
      Added value: +{
+  "default": 0.02,
+  "description": "Value for af_increment.",
+  "title": "Af Increment",
+  "type": "number"
+}
    • addedInput schema / properties / af_max
      Added value: +{
+  "default": 0.2,
+  "description": "Value for af_max.",
+  "title": "Af Max",
+  "type": "number"
+}
    • addedInput schema / properties / af_start
      Added value: +{
+  "default": 0.02,
+  "description": "Value for af_start.",
+  "title": "Af Start",
+  "type": "number"
+}
    • changedInput schema / properties / end_date / default
      Previous value: -"2026-07-09"New value: +"2026-07-14"
    • changedInput schema / properties / indicator / enum
      Previous value: -[
-  "get_moving_average",
-  "get_exponential_moving_average",
-  "get_double_exponential_moving_average",
-  "get_trix",
-  "get_triangular_moving_average"
-]New value: +[
+  "get_moving_average",
+  "get_exponential_moving_average",
+  "get_double_exponential_moving_average",
+  "get_trix",
+  "get_triangular_moving_average",
+  "get_weighted_moving_average",
+  "get_hull_moving_average",
+  "get_volume_weighted_average_price",
+  "get_parabolic_sar",
+  "get_pivot_points"
+]
    • 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"
  4. Changed2 schema fields changedv2.1.4
    • 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"
  5. Changed2 schema fields changedv2.1.3
    • 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"
  6. Changed4 schema fields changedv0.1.2
    • 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"
  7. Addedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and openWorld, so the safety profile is covered. The description adds useful context that prices are fetched automatically and tickers accept comma-separated values. It adds nothing about how indicator-specific parameters behave or what happens with unknown tickers.

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?

Front-loaded with the core purpose and the two operational facts that matter (auto price fetch, tickers syntax). Reasonably tight, though the full enumeration of 13 indicator names duplicates the schema enum and consumes tokens 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?

A 21-parameter tool with only 1 required parameter is complex, and the description leaves the relationship between parameters and the chosen indicator unexplained (e.g., that af_start/af_increment/af_max apply only to get_parabolic_sar, or that window defaults differ per indicator). The output schema covers return values, so that omission is acceptable, but the parameter-to-indicator mapping gap is significant.

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 21 parameters, including tickers formatting and the indicator enum. The description only repeats the tickers format and lists the indicator values verbatim, adding no meaning beyond the structured fields (e.g., which params apply to which indicator).

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?

States a specific verb+resource combination: computing overlapping technical indicators (SMA, EMA, Bollinger, Keltner) on price data. The category name 'overlap' is TA jargon, but the parenthetical examples make the intent concrete. It does not distinguish itself from category siblings like momentum or volatility, which also compute 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 some framing ('applied to price data automatically — no need to fetch prices first') and usage syntax for tickers, which implies how to call it. But it never says when to pick this over momentum/volatility/performance or other indicator categories, and it falsely asserts tickers is required when the schema lists only 'indicator' as required.

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

Deploy Server

Other Tools