Skip to main content
Glama
JerBouma

Finance Toolkit

quant_performance

Read-onlyIdempotent

Calculate risk-adjusted performance metrics such as Sharpe ratio, Sortino ratio, Alpha, and Beta using financial data. Requires ticker symbols and an indicator name.

Instructions

Pre-computed risk-adjusted performance metrics (Sharpe ratio, Sortino ratio, Alpha, Beta, CAPM, Fama-French factors). 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_alpha, get_beta, get_capital_asset_pricing_model, get_compound_growth_rate, get_factor_asset_correlations, get_factor_correlations, get_fama_and_french_model, get_information_ratio, get_jensens_alpha, get_m2_ratio, get_sharpe_ratio, get_sortino_ratio, get_tracking_error, get_treynor_ratio, get_ulcer_performance_index.

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'.
show_full_resultsNoValue for show_full_results.
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.
rollingNoValue for rolling.
factors_to_calculateNoComma-separated factor names to include in the calculation.
exclude_risk_freeNoValue for exclude_risk_free.
methodNoValue for method.multi
include_daily_residualsNoValue for include_daily_residuals.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, and non-destructive. The description adds context: pre-computed metrics, no daily period support, and required indicator. It does not describe response format or side effects, but annotations cover safety. The description adds value 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?

Two sentences with key information, followed by a clean list of indicators. Front-loaded with purpose and constraints. Every word earns its place.

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 complexity (16 parameters, output schema exists), the description covers the core purpose, key usage constraints, and available indicators. It does not explain every parameter, but the schema has descriptions. The output schema handles return values. Slightly more detail on benchmark_ticker or other parameters could improve, but sufficient.

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 coverage is 100% with descriptions. The description enriches key parameters: tickers (example usage), period (unsupported daily), and indicator (omission returns list). This adds meaning beyond the schema, though not all 16 parameters are covered in the description.

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 computes risk-adjusted performance metrics and lists examples (Sharpe, Sortino, etc.). It identifies the resource (performance metrics) and the verb (computes). However, it does not explicitly differentiate from sibling tools like quant_risk, so it loses a point.

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?

Provides explicit constraints: requires tickers='AAPL', comma-separated for multiple, and does not support daily period. Also explains that omitting indicator returns the list. However, it lacks comparison to alternative tools or explicit when-to-use 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