Skip to main content
Glama
Finance Toolkit

Finance Toolkit

solvency

Read-onlyIdempotent

Calculate pre-computed solvency and credit ratios—debt-to-equity, interest coverage, FFO to debt—plus operating, financial, and total leverage for one or more tickers.

Instructions

Pre-computed solvency ratios (debt-to-equity, interest coverage, debt-to-assets, net debt to EBITDA), the credit ratios of the rating agencies (EBITDA interest coverage, (EBITDA - CapEx) interest coverage, cash interest coverage, funds from operations (FFO) to debt and discretionary cash flow (DCF) to debt as defined by S&P Global Ratings) and the degrees of operating, financial and total leverage (DOL, DFL, DTL: the percentage change in operating income or net income per percentage change in revenue or operating income, year over year on quarterly data). FFO and DCF to debt use the trailing twelve months on quarterly data. Requires tickers='AAPL' — use comma-separated values for multiple tickers. Use instead of raw financial statements. Supports quarterly=true and start_date/end_date. basket=true also adds up the tickers into one company, 'Total', whose ratios are calculated on the summed statements (e.g. the capex coverage of a group of companies together, not an average of their ratios); per-share ratios stay empty for it. For the predictive power of these ratios across tickers (factor analysis), use the valuation tool with indicator='get_factor_analysis' and metrics='solvency'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "indicator": "<indicator>"
    },
    "name": "solvency"
  }
}

Input Schema

NameRequiredDescriptionDefault
lagNoNumber of periods to lag when computing growth rates.
rankNotrue ranks the tickers (or countries) within every period, from the highest value (rank 1) to the lowest, and compares each with its neighbour toward the middle of the ranking: the Difference (in points for returns) and the Multiple (only when both have the same sign), so the first and last rank show how far the best and the worst stand apart, e.g. a fall more than twice as large as the next one. Needs a value per period and ticker; pick one field with show_columns where there are more.
limitNoThe rows to return, like head and tail: 5 for the first five, -5 for the last five (the most recent of a time series). A table with its periods as columns (financial statements, ratios) keeps its first or last periods instead, and rows per ticker (an earnings calendar) are selected per ticker. For ETF holdings the largest (or, negative, the smallest) by weight, and for a list (e.g. news or a screener) its length. 0 returns every row.
basketNoAlso analyse the tickers as one company, 'Total': its statements are the sums of theirs and its ratios are calculated on those sums (per-share figures stay empty).
growthNoReturn period-over-period growth rates instead of absolute values.
dilutedNoWhether to use diluted shares for market capitalization.
tickersNoComma-separated ticker symbols, e.g. 'AAPL,MSFT,GOOGL'.
compoundNoWith growth=true, return the compound annual growth rate (CAGR) over the lag instead of the total change, e.g. lag=5 for the five-year CAGR (lag=20 with quarterly=true). Missing when either value is zero or negative.
end_dateNoEnd of the date range in YYYY-MM-DD format; left empty, today (or the indicator's own window).
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, one of the listed values. Required — search_metrics finds the indicator (and its tool) for a metric by name.
quarterlyNoReturn quarterly data instead of annual when True.
show_dailyNoWhether to show daily values: the close of each trading day against the statement figures of the latest period that has ended on or before that day (also when it ended before the start date), so no figures are used before their period closes.
start_dateNoStart of the date range in YYYY-MM-DD format; left empty, five years before today (or the indicator's own window).
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'; 'None' for no benchmark.SPY

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.3.4
    • addedInput schema / properties / basket
      Added value: +{
      +  "default": false,
      +  "description": "Also analyse the tickers as one company, 'Total': its statements are the sums of theirs and its ratios are calculated on those sums (per-share figures stay empty).",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / rank
      Added value: +{
      +  "default": false,
      +  "description": "true ranks the tickers (or countries) within every period, from the highest value (rank 1) to the lowest, and compares each with its neighbour toward the middle of the ranking: the Difference (in points for returns) and the Multiple (only when both have the same sign), so the first and last rank show how far the best and the worst stand apart, e.g. a fall more than twice as large as the next one. Needs a value per period and ticker; pick one field with show_columns where there are more.",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changedv2.3.3
    • changedInput schema / properties / indicator / enum
      Previous value: -[
      -  "get_debt_to_assets_ratio",
      -  "get_asset_coverage_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_gross_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"
      -]New value: +[
      +  "get_debt_to_assets_ratio",
      +  "get_asset_coverage_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_gross_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",
      +  "get_ebitda_interest_coverage_ratio",
      +  "get_ebitda_minus_capex_interest_coverage_ratio",
      +  "get_cash_interest_coverage_ratio",
      +  "get_funds_from_operations_to_debt_ratio",
      +  "get_discretionary_cash_flow_to_debt_ratio",
      +  "get_degree_of_operating_leverage",
      +  "get_degree_of_financial_leverage",
      +  "get_degree_of_total_leverage"
      +]
  3. Changed3 schema fields changedv2.3.2
    • addedInput schema / properties / compound
      Added value: +{
      +  "default": false,
      +  "description": "With growth=true, return the compound annual growth rate (CAGR) over the lag instead of the total change, e.g. lag=5 for the five-year CAGR (lag=20 with quarterly=true). Missing when either value is zero or negative.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"The rows to return, like head and tail: 5 for the first five, -5 for the last five (the most recent of a time series). A table with its periods as columns (financial statements, ratios) keeps its first or last periods instead. For ETF holdings the largest (or, negative, the smallest) by weight, and for a list (e.g. news or a screener) its length. 0 returns every row."New value: +"The rows to return, like head and tail: 5 for the first five, -5 for the last five (the most recent of a time series). A table with its periods as columns (financial statements, ratios) keeps its first or last periods instead, and rows per ticker (an earnings calendar) are selected per ticker. For ETF holdings the largest (or, negative, the smallest) by weight, and for a list (e.g. news or a screener) its length. 0 returns every row."
    • changedInput schema / properties / show_daily / description
      Previous value: -"Whether to show daily values: the close of each trading day against the statement figures of the latest period that has ended on or before that day, so no figures are used before their period closes."New value: +"Whether to show daily values: the close of each trading day against the statement figures of the latest period that has ended on or before that day (also when it ended before the start date), so no figures are used before their period closes."
  4. Changed6 schema fields changedv2.3.1
    • changedInput schema / properties / benchmark_ticker / description
      Previous value: -"Ticker used as the market benchmark, e.g. 'SPY' or '^GSPC'."New value: +"Ticker used as the market benchmark, e.g. 'SPY' or '^GSPC'; 'None' for no benchmark."
    • changedInput schema / properties / end_date / default
      Previous value: -"2026-10-27"New value: +""
    • changedInput schema / properties / end_date / description
      Previous value: -"End of the date range in YYYY-MM-DD format."New value: +"End of the date range in YYYY-MM-DD format; left empty, today (or the indicator's own window)."
    • changedInput schema / properties / limit / description
      Previous value: -"The rows to return, like head and tail: 5 for the first five, -5 for the last five (the most recent of a time series). A table with its periods as columns (financial statements, ratios) keeps its first or last periods instead. For ETF holdings the largest (or, negative, the smallest) by weight, and for a list (e.g. news or a screener) its length."New value: +"The rows to return, like head and tail: 5 for the first five, -5 for the last five (the most recent of a time series). A table with its periods as columns (financial statements, ratios) keeps its first or last periods instead. For ETF holdings the largest (or, negative, the smallest) by weight, and for a list (e.g. news or a screener) its length. 0 returns every row."
    • changedInput schema / properties / start_date / default
      Previous value: -"2021-10-28"New value: +""
    • changedInput schema / properties / start_date / description
      Previous value: -"Start of the date range in YYYY-MM-DD format."New value: +"Start of the date range in YYYY-MM-DD format; left empty, five years before today (or the indicator's own window)."
  5. Changed3 schema fields changedv2.3.0
    • changedInput schema / properties / end_date / default
      Previous value: -"2026-10-14"New value: +"2026-10-27"
    • changedInput schema / properties / show_daily / description
      Previous value: -"Whether to use daily data for the calculation."New value: +"Whether to show daily values: the close of each trading day against the statement figures of the latest period that has ended on or before that day, so no figures are used before their period closes."
    • changedInput schema / properties / start_date / default
      Previous value: -"2021-10-15"New value: +"2021-10-28"
  6. Changed24 schema fields changedv2.2.3
    • removedInput schema / properties / benchmark_ticker / title
      Removed value: -"Benchmark Ticker"
    • changedInput schema / properties / diluted / description
      Previous value: -"Value for diluted."New value: +"Whether to use diluted shares for market capitalization."
    • removedInput schema / properties / diluted / title
      Removed value: -"Diluted"
    • changedInput schema / properties / end_date / default
      Previous value: -"2026-10-02"New value: +"2026-10-14"
    • removedInput schema / properties / end_date / title
      Removed value: -"End Date"
    • removedInput schema / properties / growth / title
      Removed value: -"Growth"
    • changedInput schema / properties / indicator / description
      Previous value: -"Name of the specific metric to calculate, e.g. 'get_asset_turnover_ratio'. Required — omitting it returns the list of available indicators."New value: +"Name of the specific metric to calculate, one of the listed values. Required — search_metrics finds the indicator (and its tool) for a metric by name."
    • removedInput schema / properties / indicator / title
      Removed value: -"Indicator"
    • addedInput schema / properties / lag / anyOf
      Added value: +[
      +  {
      +    "type": "integer"
      +  },
      +  {
      +    "items": {
      +      "type": "integer"
      +    },
      +    "type": "array"
      +  }
      +]
    • removedInput schema / properties / lag / title
      Removed value: -"Lag"
    • removedInput schema / properties / lag / type
      Removed value: -"integer"
    • addedInput schema / properties / limit
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "The rows to return, like head and tail: 5 for the first five, -5 for the last five (the most recent of a time series). A table with its periods as columns (financial statements, ratios) keeps its first or last periods instead. For ETF holdings the largest (or, negative, the smallest) by weight, and for a list (e.g. news or a screener) its length."
      +}
    • removedInput schema / properties / quarterly / title
      Removed value: -"Quarterly"
    • removedInput schema / properties / show_columns / title
      Removed value: -"Show Columns"
    • changedInput schema / properties / show_daily / description
      Previous value: -"Value for show_daily."New value: +"Whether to use daily data for the calculation."
    • removedInput schema / properties / show_daily / title
      Removed value: -"Show Daily"
    • removedInput schema / properties / standardize / title
      Removed value: -"Standardize"
    • changedInput schema / properties / start_date / default
      Previous value: -"2021-10-03"New value: +"2021-10-15"
    • removedInput schema / properties / start_date / title
      Removed value: -"Start Date"
    • addedInput schema / properties / tickers / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  }
      +]
    • removedInput schema / properties / tickers / title
      Removed value: -"Tickers"
    • removedInput schema / properties / tickers / type
      Removed value: -"string"
    • removedInput schema / properties / trailing / title
      Removed value: -"Trailing"
    • removedInput schema / title
      Removed value: -"solvencyArguments"
  7. Changed2 schema fields changedv2.2.1
    • changedInput schema / properties / end_date / default
      Previous value: -"2026-08-19"New value: +"2026-10-02"
    • changedInput schema / properties / start_date / default
      Previous value: -"2021-08-20"New value: +"2021-10-03"
  8. Changed3 schema fields changedv2.2.0
    • changedInput schema / properties / end_date / default
      Previous value: -"2026-07-14"New value: +"2026-08-19"
    • changedInput schema / properties / indicator / enum
      Previous value: -[
      -  "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"
      -]New value: +[
      +  "get_debt_to_assets_ratio",
      +  "get_asset_coverage_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_gross_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"
      +]
    • changedInput schema / properties / start_date / default
      Previous value: -"2021-07-15"New value: +"2021-08-20"
  9. Changed5 schema fields changed
    • changedInput schema / properties / end_date / default
      Previous value: -"2026-07-09"New value: +"2026-07-14"
    • changedInput schema / properties / indicator / enum
      Previous value: -[
      -  "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"
      -]New value: +[
      +  "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"
      +]
    • addedInput schema / properties / standardize
      Added value: +{
      +  "default": false,
      +  "description": "Return 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.",
      +  "title": "Standardize",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / start_date / default
      Previous value: -"2021-07-10"New value: +"2021-07-15"
    • changedInput schema / properties / trailing / description
      Previous value: -"Number of trailing periods for rolling-window calculations."New value: +"Trailing 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."
  10. Changed2 schema fields changedv2.1.4
    • changedInput schema / properties / end_date / default
      Previous value: -"2026-06-27"New value: +"2026-07-09"
    • changedInput schema / properties / start_date / default
      Previous value: -"2021-06-28"New value: +"2021-07-10"
  11. Changed2 schema fields changedv2.1.3
    • changedInput schema / properties / end_date / default
      Previous value: -"2026-06-23"New value: +"2026-06-27"
    • changedInput schema / properties / start_date / default
      Previous value: -"2021-06-24"New value: +"2021-06-28"
  12. Changed4 schema fields changedv0.1.2
    • changedInput schema / properties / end_date / default
      Previous value: -"2026-06-22"New value: +"2026-06-23"
    • removedInput schema / properties / rounding
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "integer"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "Number of decimal places to round results to.",
      -  "title": "Rounding"
      -}
    • addedInput schema / properties / show_columns
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Comma-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.",
      +  "title": "Show Columns"
      +}
    • changedInput schema / properties / start_date / default
      Previous value: -"2021-06-23"New value: +"2021-06-24"
  13. Addedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds real behavioral detail beyond them: FFO and DCF-to-debt use trailing-twelve-month quarterly data, the leverage degrees are computed year-over-year on quarterly data, and basket=true sums statements rather than averaging ratios while leaving per-share ratios empty — non-obvious semantics worth disclosing. It stops short of error, rate-limit, or missing-data behavior, so it is not a 5.

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 ratio inventory is front-loaded, which is good, but the whole definition is one long undifferentiated paragraph that mixes purpose, formulas, parameter guidance, and cross-tool routing. Nothing is wasted exactly, yet the density and lack of structure make it harder to scan than it needs to be.

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?

With 17 parameters, one required indicator enum, an output schema, and annotations present, the definition covers the important call decisions — required tickers, quarterly, start/end dates, basket aggregation, and where to go for factor analysis. The output schema carries the return-value burden, so the remaining gap (error handling, partial-data behavior) is minor.

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% and all 17 parameters are documented in the schema, so baseline is 3. The description still adds meaning on top: it clarifies the comma-separated ticker format, explains that basket aggregates summed statements rather than averaging ratios (and that per-share figures go blank), and ties quarterly/start_date/end_date to how the ratios are computed, going beyond the schema's own wording.

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 names the exact resource family (solvency ratios: debt-to-equity, interest coverage, debt-to-assets, net debt to EBITDA, the S&P credit ratios, and DOL/DFL/DTL) and states a concrete verb (pre-computed/return). It also distinguishes itself from raw financial statements and from the valuation tool's factor analysis, so an agent can separate it from siblings like profitability, efficiency, or valuation without opening a schema.

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

Usage Guidelines5/5

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

It gives explicit routing rules: 'Use instead of raw financial statements' and 'For the predictive power of these ratios across tickers (factor analysis), use the valuation tool with indicator=get_factor_analysis and metrics=solvency.' It also states the required tickers argument and the basket/quarterly modes, leaving little to inference about when to pick this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.