Skip to main content
Glama
JerBouma

Finance Toolkit

by JerBouma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

breadth

Read-onlyIdempotent

Compute technical indicators like McClellan Oscillator and OBV for specified tickers. Automatically uses price data, so no need to fetch prices first.

Instructions

Market breadth technical indicators (McClellan Oscillator, OBV, Advance/Decline Line, Chaikin). Applied to price data automatically — no need to fetch prices first. Requires tickers='AAPL' — use comma-separated values for multiple tickers.

Available indicators: get_mcclellan_oscillator, get_advancers_decliners, get_on_balance_volume, get_accumulation_distribution_line, get_chaikin_oscillator, get_trin, get_new_highs_new_lows, get_chaikin_money_flow, get_ease_of_movement, get_negative_volume_index, get_positive_volume_index.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lagNoNumber of periods to lag when computing growth rates.
growthNoReturn period-over-period growth rates instead of absolute values.
periodNoObservation frequency, e.g. 'monthly', 'quarterly', or 'annual'.daily
windowNoValue for window. Leave unset to use the default of the indicator you selected. Defaults are 14 for get_ease_of_movement; 20 for get_chaikin_money_flow; 252 for get_new_highs_new_lows.
tickersNoComma-separated ticker symbols, e.g. 'AAPL,MSFT,GOOGL'.
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
long_windowNoValue for long_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.
start_valueNoValue for start_value.
close_columnNoValue for close_column.Adj Close
short_windowNoValue for short_window.
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.
volume_divisorNoValue for volume_divisor.
long_ema_windowNoValue for long_ema_window.
benchmark_tickerNoTicker used as the market benchmark, e.g. 'SPY' or '^GSPC'.SPY
short_ema_windowNoValue for short_ema_window.

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. Changed9 schema fields changedv2.2.0
    • changedInput schema / properties / end_date / default
      Previous value: -"2026-07-14"New value: +"2026-08-19"
    • changedInput schema / properties / indicator / enum
      Previous value: -[
-  "get_mcclellan_oscillator",
-  "get_advancers_decliners",
-  "get_on_balance_volume",
-  "get_accumulation_distribution_line",
-  "get_chaikin_oscillator",
-  "get_trin",
-  "get_new_highs_new_lows"
-]New value: +[
+  "get_mcclellan_oscillator",
+  "get_advancers_decliners",
+  "get_on_balance_volume",
+  "get_accumulation_distribution_line",
+  "get_chaikin_oscillator",
+  "get_trin",
+  "get_new_highs_new_lows",
+  "get_chaikin_money_flow",
+  "get_ease_of_movement",
+  "get_negative_volume_index",
+  "get_positive_volume_index"
+]
    • changedInput schema / properties / start_date / default
      Previous value: -"2021-07-15"New value: +"2021-08-20"
    • addedInput schema / properties / start_value
      Added value: +{
+  "default": 1000,
+  "description": "Value for start_value.",
+  "title": "Start Value",
+  "type": "number"
+}
    • addedInput schema / properties / volume_divisor
      Added value: +{
+  "default": 100000000,
+  "description": "Value for volume_divisor.",
+  "title": "Volume Divisor",
+  "type": "number"
+}
    • addedInput schema / properties / window / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / window / default
      Previous value: -252New 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 are 14 for get_ease_of_movement; 20 for get_chaikin_money_flow; 252 for get_new_highs_new_lows."
    • removedInput schema / properties / window / type
      Removed value: -"integer"
  3. Changed5 schema fields changed
    • changedInput schema / properties / end_date / default
      Previous value: -"2026-07-09"New value: +"2026-07-14"
    • changedInput schema / properties / indicator / enum
      Previous value: -[
-  "get_mcclellan_oscillator",
-  "get_advancers_decliners",
-  "get_on_balance_volume",
-  "get_accumulation_distribution_line",
-  "get_chaikin_oscillator"
-]New value: +[
+  "get_mcclellan_oscillator",
+  "get_advancers_decliners",
+  "get_on_balance_volume",
+  "get_accumulation_distribution_line",
+  "get_chaikin_oscillator",
+  "get_trin",
+  "get_new_highs_new_lows"
+]
    • 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"
    • addedInput schema / properties / window
      Added value: +{
+  "default": 252,
+  "description": "Value for window.",
+  "title": "Window",
+  "type": "integer"
+}
  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

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, openWorld), so the bar is lower, yet the description still adds real behavior: automatic price fetching, the tickers precondition, and that omitting the indicator returns the available-indicator list. It does not mention rate limits or the cost of the 19-parameter surface, but the added context is meaningful.

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?

Two short blocks, front-loaded with the domain and the auto-fetch behavior, followed by the indicator list. The indicator enumeration mirrors the enum but is reasonable given the tool's dispatch-style design; no filler sentences.

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 19-parameter dispatcher with an output schema, the description covers the required selection (indicator), the data precondition (tickers), and the discovery behavior (omitting indicator lists options). Remaining details — window defaults, benchmark_ticker, show_columns — are fully specified in the schema, so nothing critical is missing.

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 all 19 parameters are already documented with defaults (window defaults per indicator, standardize, growth, etc.). The description only restates the tickers comma-separated format and the indicator requirement, adding little beyond the schema — the baseline 3 for high coverage applies.

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 names the specific resource domain ('Market breadth technical indicators') and enumerates the exact indicator family it computes (McClellan, OBV, A/D, Chaikin), so an agent can tell it apart from momentum/volatility siblings by scope. It does not explicitly contrast itself with those siblings, which is the only thing keeping it from a 5.

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 one genuinely useful routing hint ('Applied to price data automatically — no need to fetch prices first') and a precondition (tickers must be set). However it never says when to choose breadth versus momentum/volatility/performance siblings, 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.

Deploy Server

Other Tools