Skip to main content
Glama
JerBouma

Finance Toolkit

risk

Read-onlyIdempotent

Compute pre-computed risk metrics such as VaR, CVaR, GARCH volatility, max drawdown, skewness, and kurtosis for given tickers. Select an indicator to assess portfolio risk.

Instructions

Pre-computed risk metrics (VaR, CVaR, GARCH volatility, max drawdown, skewness, kurtosis). Requires tickers='AAPL' — use comma-separated values for multiple tickers. Does NOT support period='daily'; use weekly, monthly, quarterly, or yearly instead.

Available indicators: get_conditional_value_at_risk, get_entropic_value_at_risk, get_garch, get_garch_forecast, get_kurtosis, get_maximum_drawdown, get_skewness, get_ulcer_index, get_value_at_risk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lagNoNumber of periods to lag when computing growth rates.
alphaNoValue for alpha.
fisherNoValue for fisher.
growthNoReturn period-over-period growth rates instead of absolute values.
periodNoObservation frequency, e.g. 'monthly', 'quarterly', or 'annual'.
rollingNoValue for rolling.
tickersNoComma-separated ticker symbols, e.g. 'AAPL,MSFT,GOOGL'.
end_dateNoEnd of the date range in YYYY-MM-DD format.2026-06-27
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
time_stepsNoValue for time_steps.
distributionNoValue for distribution.historic
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.
within_periodNoValue for within_period.
optimization_tNoValue for optimization_t.
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?

Annotations declare readOnlyHint, openWorldHint, and idempotentHint, establishing safety. The description adds value by specifying that tickers are required, daily period is not supported, and listing available indicators. This contextualizes behavior beyond annotations.

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 tight paragraphs. The first paragraph states purpose and key constraints; the second lists indicators. Every sentence adds value without redundancy.

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 tool has 17 parameters and an output schema, the description covers essential aspects: purpose, key parameter constraints (tickers, period), and available indicators. It does not explain each indicator or output format, but the schema handles those. The description is sufficiently complete for the complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, providing a baseline of 3. The description adds meaning by clarifying the tickers requirement (despite default empty) and explicitly stating that period='daily' is unsupported, which is not fully captured in the schema. It also lists available indicators, aiding understanding of the 'indicator' parameter.

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 identifies the tool's purpose: providing pre-computed risk metrics (VaR, CVaR, etc.) and lists available indicators. While it distinguishes from sibling tools (e.g., 'momentum') by focusing on risk, it does not explicitly contrast with alternatives.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus siblings. The description mentions required tickers and unsupported daily period but does not provide criteria for choosing this tool over related tools like 'volatility' or 'momentum'.

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