Skip to main content
Glama
JerBouma

Finance Toolkit

performance

Read-onlyIdempotent

Retrieve risk-adjusted performance metrics like Sharpe and Sortino ratios, Alpha, Beta, CAPM, and Fama-French factors for ticker symbols. Specify period: weekly, monthly, quarterly, or yearly.

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
lagNoNumber of periods to lag when computing growth rates.
growthNoReturn period-over-period growth rates instead of absolute values.
methodNoValue for method.multi
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
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
exclude_risk_freeNoValue for exclude_risk_free.
show_full_resultsNoValue for show_full_results.
factors_to_calculateNoComma-separated factor names to include in the calculation.
include_daily_residualsNoValue for include_daily_residuals.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds significant behavioral context: it lists available indicators, states that omitting 'indicator' returns the list, and clarifies the period constraint ('daily' not supported). No contradictions with 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 and well-structured: it starts with the tool's purpose, then gives specific usage requirements, and ends with the indicator list. 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 16 parameters, 100% schema coverage, annotations, and an output schema, the description adequately covers the main functionality and key constraints. However, it does not explain parameters like 'lag', 'rolling', etc., but the schema compensates. Minor inconsistency: description says tickers are required, but schema shows optional.

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%, so baseline is 3. The description adds value by explaining the 'indicator' parameter's behavior (required, returns list if omitted) and the ticker and period constraints. Other parameters are not elaborated but schema descriptions are sufficient.

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 that the tool computes risk-adjusted performance metrics like Sharpe ratio, Sortino ratio, etc., and distinguishes it from sibling tools by focusing on performance metrics. It specifies the required ticker format and unsupported period, making its purpose unmistakable.

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 explicit usage guidance, including how to specify tickers ('AAPL' or comma-separated values) and which periods are supported (not daily). However, it does not compare with sibling tools or explain when not to use it, missing full contextual 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