Skip to main content
Glama
JerBouma

Finance Toolkit

by JerBouma

volatility

Read-onlyIdempotent

Calculate volatility technical indicators including ATR, Bollinger Bands, and Keltner Channels for specified tickers using historical price data.

Instructions

Volatility technical indicators (ATR, True Range). Applied to price data automatically — no need to fetch prices first. Requires tickers='AAPL' — use comma-separated values for multiple tickers.

Available indicators: get_bollinger_bands, get_true_range, get_average_true_range, get_keltner_channels, get_donchian_channels.

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'.
end_dateNoEnd of the date range in YYYY-MM-DD format.2026-07-14
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.
atr_windowNoValue for atr_window.
start_dateNoStart of the date range in YYYY-MM-DD format.2021-07-15
num_std_devNoValue for num_std_dev.
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.
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.
atr_multiplierNoValue for atr_multiplier.
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?

The description adds behavioral context beyond annotations: it reveals that price data is fetched automatically (saving a step) and that tickers are needed. This complements the readOnlyHint and idempotentHint 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise: two sentences plus a list of indicators. It is front-loaded with the core purpose and adds no redundant information. Every sentence serves a purpose.

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 has 16 parameters and an output schema, the description is adequate but could be more complete. It explains the auto-fetching behavior and lists indicators, but does not guide how parameters like 'window' or 'num_std_dev' interact with specific indicators. The output schema exists, so return values are covered.

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 baseline is 3. The description reiterates that the 'indicator' parameter is required and provides example tickers usage, but does not significantly add meaning beyond the schema. Minor inconsistency: describes tickers as required (it has a default, so not required).

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 the tool provides volatility indicators (ATR, True Range) and lists available indicators. It distinguishes itself by noting price data is fetched automatically. However, it does not explicitly differentiate from sibling tools like 'momentum' which also compute technical 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?

The description provides usage context by stating that price data is retrieved automatically and that tickers are required. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., 'momentum'), and does not specify when not to use it.

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