Skip to main content
Glama
JerBouma

Finance Toolkit

by JerBouma

overlap

Read-onlyIdempotent

Calculate technical indicators like moving averages, Bollinger Bands, and Keltner Channels directly from price data. Specify tickers and indicator to get results automatically.

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-08-19
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-08-20
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
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description adds that price data is fetched automatically (no need to fetch prices first) and enumerates available indicators. Minor limitation: no mention of output format or rate limits, but annotations cover critical side-effect aspects.

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 organized into two short paragraphs. The list of indicators is redundant with the schema enum, but it adds a quick reference. No filler or excessive detail.

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 complex input schema, the description provides helpful context (price data handling, indicator list) but omits a clear definition of 'overlap' and lacks guidance on parameter interactions. The presence of an output schema may cover return formatting, but the description alone is 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?

The description clarifies 'tickers' and 'indicator' (comma-separated, list of options) and 'show_columns' indirectly. However, many parameters (af_start, af_increment, sensitivity) have generic 'Value for X' descriptions in the schema, and the description does not enrich them. Schema coverage is 100% but semantics are weak for most parameters.

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 states the tool computes technical overlap indicators (SMA, EMA, Bollinger Bands, Keltner Channels) and lists available indicators. It clearly identifies the resource (price data) and the general action, but could be more precise about the 'overlap' concept and differentiate from sibling categories.

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 implies usage for overlap indicators and notes no need to fetch prices separately, but does not explicitly contrast with sibling tools like momentum or volatility. It lacks clear when-to-use vs alternatives guidance.

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