Skip to main content
Glama
JerBouma

Finance Toolkit

by JerBouma

solvency

Read-onlyIdempotent

Compute solvency ratios such as debt-to-equity and interest coverage. Choose from 12 indicators for multiple tickers with quarterly or historical data.

Instructions

Pre-computed solvency ratios (debt-to-equity, interest coverage, debt-to-assets, net debt to EBITDA). 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_debt_to_assets_ratio, get_debt_to_equity_ratio, get_debt_service_coverage_ratio, get_equity_multiplier, get_free_cash_flow_yield, get_net_debt_to_ebitda_ratio, get_cash_flow_coverage_ratio, get_capex_coverage_ratio, get_capex_dividend_coverage_ratio, get_debt_to_capital_ratio, get_preferred_dividend_coverage_ratio, get_interest_paid_to_expense_ratio.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lagNoNumber of periods to lag when computing growth rates.
growthNoReturn period-over-period growth rates instead of absolute values.
dilutedNoValue for diluted.
tickersNoComma-separated ticker symbols, e.g. 'AAPL,MSFT,GOOGL'.
end_dateNoEnd of the date range in YYYY-MM-DD format.2026-07-14
trailingNoTrailing window size in number of periods. Sums the raw values over the trailing N periods (e.g. trailing=4 on quarterly data gives a trailing-4-quarter / TTM-style sum) instead of returning one value per period.
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.
show_dailyNoValue for show_daily.
start_dateNoStart of the date range in YYYY-MM-DD format.2021-07-15
standardizeNoReturn the Z-Score (standard score) instead of the raw values, i.e. how many standard deviations each value is from the mean of its own series. When combined with growth=True, the growth values are standardized instead of the raw values.
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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds that the tool returns pre-computed ratios (no calculation), requires tickers, and lists available indicators. No contradiction 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.

Conciseness3/5

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

The description is front-loaded with purpose and usage, but it redundantly lists all indicators which are already in the schema as an enum. The list is long and could be omitted for conciseness.

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 13 parameters (1 required), 100% schema coverage, and an output schema, the description provides sufficient context: pre-computed nature, ticker requirement, date range support, and the behavior of the indicator parameter. It covers key usage points without significant gaps.

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 that omitting the required 'indicator' returns the list of available indicators and gives a usage example for 'tickers'. Other parameter details are adequately covered by schema descriptions.

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 pre-computed solvency ratios, lists example ratios, and distinguishes from raw financial statements. It also enumerates all available indicators, making the purpose specific and distinct from sibling tools like profitability or liquidity.

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?

Explicitly advises to 'Use instead of raw financial statements' and mentions support for quarterly data and date ranges. However, it does not specify when not to use this tool or provide direct alternatives among siblings.

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