Skip to main content
Glama
JerBouma

Finance Toolkit

technicals_volatility

Read-onlyIdempotent

Compute volatility indicators such as ATR, Bollinger Bands, and True Range for any stock tickers using historical price data. Automatically fetches and processes 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.

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.
num_std_devNoValue for num_std_dev.
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.
atr_windowNoValue for atr_window.
atr_multiplierNoValue for atr_multiplier.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, covering safety and idempotency. The description adds the behavioral trait of auto-applying to price data, which is useful but not extensive.

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 concise with two sentences and a bullet list. It front-loads the purpose and key requirements, with no superfluous information.

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?

Given the 15 parameters with full schema descriptions, annotations, and an output schema, the description provides adequate context. It covers the tool's scope, usage, and key behavioral traits, though it could mention the output format briefly.

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%, and the description adds minimal value beyond the schema. It emphasizes that tickers is required and comma-separated, but this is redundant with the schema description.

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?

The description clearly states it provides volatility technical indicators (ATR, True Range) and lists the specific available indicators. It distinguishes itself from sibling tools like technicals_breadth and technicals_momentum by focusing on volatility metrics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage context: it auto-applies to price data (no prefetching) and requires tickers in comma-separated format. However, it does not explicitly state when not to use or mention alternatives for other volatility indicators not listed.

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