Skip to main content
Glama
JerBouma

Finance Toolkit

ratios_liquidity

Read-onlyIdempotent

Assess short-term financial health with pre-computed liquidity ratios (current, quick, cash, working capital) for any stock ticker. Supports quarterly data and custom date ranges.

Instructions

Pre-computed liquidity ratios (current ratio, quick ratio, cash ratio, working capital). 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_current_ratio, get_quick_ratio, get_cash_ratio, get_working_capital, get_operating_cash_flow_ratio, get_operating_cash_flow_sales_ratio, get_short_term_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.

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 and idempotentHint. The description adds that ratios are precomputed and requires tickers, and lists all available indicators. No contradictions 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.

Conciseness5/5

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

The description is two sentences plus a list. Front-loaded with purpose, no fluff. Highly efficient.

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?

Covers core functionality, required parameters, available indicators, and alternative usage. Output schema exists so return values are documented. Sufficient for agent selection.

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?

Input schema has 100% description coverage. The description adds context by showing example usage ('tickers='AAPL'', 'quarterly=true') and listing indicators, which adds value beyond 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 explicitly states the tool computes precomputed liquidity ratios such as current ratio, quick ratio, etc. It lists example tickers and indicates it is an alternative to raw financial statements, clearly distinguishing it from sibling tools like ratios_profitability.

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?

The description advises to use instead of raw financial statements and shows required parameters (tickers, indicator). It implies usage for liquidity metrics but does not explicitly list when not to use or compare to all sibling tools beyond that.

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