Skip to main content
Glama
JerBouma

Finance Toolkit

profitability

Read-onlyIdempotent

Calculate key profitability ratios including margins, returns on equity and assets, and tax rates for one or more tickers with optional quarterly and date range parameters.

Instructions

Pre-computed profitability ratios (gross margin, operating margin, net margin, ROE, ROA, ROIC, ROCE). Requires tickers='AAPL' — use comma-separated values for multiple tickers. Use instead of raw financial statements. Supports quarterly=true and start_date/end_date.

Available indicators: get_gross_margin, get_operating_margin, get_net_profit_margin, get_interest_coverage_ratio, get_income_before_tax_profit_margin, get_effective_tax_rate, get_return_on_assets, get_return_on_equity, get_return_on_invested_capital, get_return_on_capital_employed, get_return_on_tangible_assets, get_income_quality_ratio, get_net_income_per_ebt, get_free_cash_flow_operating_cash_flow_ratio, get_EBT_to_EBIT, get_EBIT_to_revenue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lagNoNumber of periods to lag when computing growth rates.
growthNoReturn period-over-period growth rates instead of absolute values.
tickersNoComma-separated ticker symbols, e.g. 'AAPL,MSFT,GOOGL'.
end_dateNoEnd of the date range in YYYY-MM-DD format.2026-06-27
trailingNoNumber of trailing periods for rolling-window calculations.
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
dividend_adjustedNoValue for dividend_adjusted.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint. Description adds that ratios are 'pre-computed' and serves as alternative to raw statements, providing useful behavioral context 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.

Conciseness4/5

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

Front-loaded with essential purpose and usage, followed by indicator list. Could be slightly more concise by omitting redundant examples, but overall well-organized and informative.

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?

Output schema exists, so return values need not be explained. Description covers key aspects: purpose, required parameter, example usage, and available indicators. Adequate for a tool with many parameters and siblings.

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 3. Description adds value by listing all indicator enum values and noting that omitting indicator returns full list. Also explains usage of tickers and date parameters beyond schema descriptions.

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?

Clear statement that tool provides pre-computed profitability ratios, with specific examples (gross margin, ROE). However, does not explicitly differentiate from sibling tools like efficiency or solvency, which measure other financial aspects.

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?

States 'Use instead of raw financial statements' and provides parameter usage examples (tickers, quarterly, dates). Lacks when-not-to-use and explicit comparisons to alternative tools.

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