Skip to main content
Glama
JerBouma

Finance Toolkit

momentum

Read-onlyIdempotent

Calculate momentum technical indicators (RSI, MACD, Stochastic, etc.) for stock tickers. Specify indicator and date range to analyze price trends.

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.

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.
tickersNoComma-separated ticker symbols, e.g. 'AAPL,MSFT,GOOGL'.
constantNoValue for constant.
end_dateNoEnd of the date range in YYYY-MM-DD format.2026-06-27
window_1NoValue for window_1.
window_2NoValue for window_2.
window_3NoValue for window_3.
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-06-28
base_windowNoValue for base_window.
long_windowNoValue for long_window.
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.
smooth_widowNoValue for smooth_widow.
signal_windowNoValue for signal_window.
benchmark_tickerNoTicker used as the market benchmark, e.g. 'SPY' or '^GSPC'.SPY
conversion_windowNoValue for conversion_window.
lead_span_b_windowNoValue for lead_span_b_window.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already indicate readOnlyHint and idempotentHint, so the tool is safe and idempotent. The description adds that price data is handled automatically, which is useful behavioral context, but it does not elaborate on data sources or limits. The description does not contradict annotations.

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?

The description is concise and front-loaded, with a clear first sentence stating purpose. The list of indicators is lengthy but necessary. There is no fluff, and every sentence contributes meaning.

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?

Given the tool's complexity (many parameters and indicators), the description covers the core concept but does not explain the roles of parameters like lag, period, or window in context. The presence of an output schema reduces the need to describe return values. It is adequate but not comprehensive.

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?

The input schema has 100% parameter coverage with descriptions, so the baseline is 3. The description adds extra meaning for the indicator parameter (omitting it returns a list) and reiterates the tickers format, but this is marginal improvement over the schema.

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 clearly states that the tool calculates momentum technical indicators (RSI, MACD, etc.) and automatically applies them to price data. It lists specific indicators, distinguishing it from sibling tools like volatility or valuation, though it does not explicitly compare itself to them.

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?

The description provides some usage guidance, such as requiring tickers and noting that comma-separated values are accepted. It also mentions that no separate price fetching is needed. However, it does not specify when to use this tool over alternatives or provide exclusions, leaving comparative guidance implicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JerBouma/FinanceToolkit'

If you have feedback or need assistance with the MCP directory API, please join our Discord server