Skip to main content
Glama
JerBouma

Finance Toolkit

by JerBouma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

solvency

Read-onlyIdempotent

Compute key leverage and coverage ratios like debt-to-equity and interest coverage for tickers to evaluate financial health without raw statements.

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_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.

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-10-02
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-10-03
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. 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"
  3. 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."
  4. 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"
  5. 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"
  6. 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"
  7. Addedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so safety and repeatability are covered without the description. The description adds the tickers requirement and the available indicator set, but discloses nothing about authentication, rate limits, or data latency, and much of what it adds duplicates the schema enum rather than extending it.

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 opening sentences are tight and front-loaded on the purpose, which is good. But the 14-item 'Available indicators' list is a verbatim restatement of the enum already in the schema, adding length without new information and diluting the useful first paragraph.

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?

An output schema exists and the schema documents all 13 parameters, so return-value and parameter explanation are not required of the description. The description covers the core call pattern (indicator + tickers, with quarterly/date options), leaving only secondary parameters like benchmark_ticker or standardize to the schema — adequate overall.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter (lag, trailing, standardize, benchmark_ticker, etc.) is already documented in structured form. The description only re-mentions tickers, quarterly, and start/end date, adding no format or edge-case meaning beyond the schema — baseline 3 is correct.

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 states a specific resource ('Pre-computed solvency ratios') and enumerates representative metrics (debt-to-equity, interest coverage, debt-to-assets, net debt to EBITDA), so the agent knows this is a ratio-computation tool rather than a raw statement fetch. It does not explicitly contrast itself with sibling category tools such as profitability or efficiency, so it stops short of a 5.

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?

It gives operational guidance ('Requires tickers=... use comma-separated values for multiple tickers', 'Use instead of raw financial statements') and notes quarterly/date support, which implies when the tool applies. However, it never names which sibling (profitability, efficiency, valuation) to pick when a ratio spans categories, so the selection guidance remains implied rather than explicit.

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

Deploy Server

Other Tools