Skip to main content
Glama
JerBouma

Finance Toolkit

technicals_momentum

Read-onlyIdempotent

Compute momentum technical indicators (RSI, MACD, Stochastic, etc.) for specified tickers; price data is retrieved and applied automatically.

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
indicatorYesName of the specific metric to calculate, e.g. 'get_asset_turnover_ratio'. Required — omitting it returns the list of available indicators.
tickersNoComma-separated ticker symbols, e.g. 'AAPL,MSFT,GOOGL'.
start_dateNoStart of the date range in YYYY-MM-DD format.2021-06-22
end_dateNoEnd of the date range in YYYY-MM-DD format.2026-06-21
quarterlyNoReturn quarterly data instead of annual when True.
benchmark_tickerNoTicker used as the market benchmark, e.g. 'SPY' or '^GSPC'.SPY
periodNoObservation frequency, e.g. 'monthly', 'quarterly', or 'annual'.daily
close_columnNoValue for close_column.Adj Close
windowNoValue for window.
roundingNoNumber of decimal places to round results to.
growthNoReturn period-over-period growth rates instead of absolute values.
lagNoNumber of periods to lag when computing growth rates.
constantNoValue for constant.
window_1NoValue for window_1.
window_2NoValue for window_2.
window_3NoValue for window_3.
short_windowNoValue for short_window.
long_windowNoValue for long_window.
conversion_windowNoValue for conversion_window.
base_windowNoValue for base_window.
lead_span_b_windowNoValue for lead_span_b_window.
smooth_widowNoValue for smooth_widow.
signal_windowNoValue for signal_window.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. Description adds the behavioral insight that price data is fetched automatically ('no need to fetch prices first'), which is beyond the annotations. No contradictions.

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?

Description is front-loaded with key information and two paragraphs. The list of indicators is long but serves as a reference. Could be slightly more compact, but overall efficient.

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?

Covers core purpose and automatic price fetching. However, with 23 parameters, it lacks guidance on which parameters apply to which indicator. Output schema exists but description does not explain output structure. Adequate but not fully complete.

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 coverage is 100%, with each parameter described. The description reiterates indicator and tickers but does not add new meaning beyond what the schema provides. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool computes momentum indicators (RSI, MACD, etc.) and explains it automatically applies to price data without needing separate price fetch. It distinguishes from sibling technical tools (breadth, overlap, volatility).

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?

Provides explicit usage: requires tickers and comma-separated values. Lists available indicators. However, it does not give guidance on when to use this tool vs alternatives (e.g., other technicals or economics tools).

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