Skip to main content
Glama
JerBouma

Finance Toolkit

ratios_solvency

Read-onlyIdempotent

Calculate solvency ratios such as debt-to-equity, interest coverage, and net debt to EBITDA for one or more tickers. Supports quarterly and custom date ranges.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indicatorYesName of the specific metric to calculate, e.g. 'get_asset_turnover_ratio'. Required — omitting it returns the list of available indicators.
tickersNoComma-separated ticker symbols, e.g. 'AAPL,MSFT,GOOGL'.
start_dateNoStart of the date range in YYYY-MM-DD format.2021-06-22
end_dateNoEnd of the date range in YYYY-MM-DD format.2026-06-21
quarterlyNoReturn quarterly data instead of annual when True.
benchmark_tickerNoTicker used as the market benchmark, e.g. 'SPY' or '^GSPC'.SPY
roundingNoNumber of decimal places to round results to.
growthNoReturn period-over-period growth rates instead of absolute values.
lagNoNumber of periods to lag when computing growth rates.
trailingNoNumber of trailing periods for rolling-window calculations.
show_dailyNoValue for show_daily.
dilutedNoValue for diluted.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already declare read-only and idempotent behavior. The description reinforces 'pre-computed' and lists available indicators but does not disclose additional behavioral traits such as data source, latency, or pagination. It adds no contradictions but minimal extra value.

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?

The description is relatively concise and front-loaded with purpose. However, it redundantly lists indicators in both the first sentence and the second paragraph. Overall length is reasonable and structure is clear, which earns a high score.

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 the comprehensive input schema (12 parameters with 100% coverage) and presence of an output schema, the description provides adequate context: purpose, usage hint, and list of indicators. Minor omissions like data source or limitations are acceptable given the schema richness.

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%, and all parameters are documented in the schema. The description merely repeats or summarizes schema information (e.g., tickers format, date range, quarterly flag) without providing additional semantic or usage context beyond what is already in the schema.

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 the tool provides pre-computed solvency ratios (debt-to-equity, etc.) and explicitly contrasts with raw financial statements. It is distinct from sibling ratio tools covering efficiency, liquidity, etc., so the purpose is specific and well-differentiated.

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?

The description advises using this tool instead of raw financial statements but provides no explicit comparison to other ratio tools like ratios_liquidity or ratios_efficiency. It lacks guidance on when to choose this over alternatives, so usage context is implied but not fully directive.

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