Finance Toolkit

Overview Schema Source Related Servers Discussions Admin

liquidity

Read-onlyIdempotent

Compute pre-computed liquidity ratios such as current, quick, and cash ratios plus working capital for one or more tickers, so you can assess short-term financial health without parsing raw statements.

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.

Input Schema

Name	Required	Description	Default
`lag`	No	Number of periods to lag when computing growth rates.
`days`	No	Number of calendar days used in day-count-based calculations.
`limit`	No	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.
`growth`	No	Return period-over-period growth rates instead of absolute values.
`tickers`	No	Comma-separated ticker symbols, e.g. 'AAPL,MSFT,GOOGL'.
`end_date`	No	End of the date range in YYYY-MM-DD format.	2026-10-27
`trailing`	No	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.
`indicator`	Yes	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.
`quarterly`	No	Return quarterly data instead of annual when True.
`start_date`	No	Start of the date range in YYYY-MM-DD format.	2021-10-28
`standardize`	No	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.
`show_columns`	No	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.
`benchmark_ticker`	No	Ticker used as the market benchmark, e.g. 'SPY' or '^GSPC'.	SPY

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.3.0Oct 27, 2026
- changedInput schema / properties / end_date / default
```
Previous value: -"2026-10-14"New value: +"2026-10-27"
```
- changedInput schema / properties / start_date / default
```
Previous value: -"2021-10-15"New value: +"2021-10-28"
```

Changed21 schema fields changedv2.2.3Oct 14, 2026

removedInput schema / properties / benchmark_ticker / title
```
Removed value: -"Benchmark Ticker"
```
removedInput schema / properties / days / title
```
Removed value: -"Days"
```

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"
```
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: -"liquidityArguments"
```

Changed2 schema fields changedv2.2.1Oct 2, 2026
- 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"
```

Changed4 schema fields changedv2.2.0Aug 19, 2026

addedInput schema / properties / days

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Number of calendar days used in day-count-based calculations.",
+  "title": "Days"
+}

changedInput schema / properties / end_date / default

Previous value: -"2026-07-14"New value: +"2026-08-19"

changedInput schema / properties / indicator / enum

Previous value: -[
-  "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"
-]New value: +[
+  "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",
+  "get_defensive_interval_ratio"
+]

changedInput schema / properties / start_date / default

Previous value: -"2021-07-15"New value: +"2021-08-20"

Changed4 schema fields changedJul 14, 2026

changedInput schema / properties / end_date / default

Previous value: -"2026-07-09"New value: +"2026-07-14"

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

Changed2 schema fields changedv2.1.4Jul 9, 2026
- 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"
```
Changed2 schema fields changedv2.1.3Jun 27, 2026
- 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"
```

Changed4 schema fields changedv0.1.2Jun 23, 2026

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"

Addedv0.1.1Jun 22, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, and openWorld, so the safety profile is covered. The description adds that values are pre-computed and covers date/periodicity scoping, but the claim "Requires tickers='AAPL'" conflicts with the schema, which lists tickers as optional with an empty default and only indicator as required — a discrepancy that could mislead an agent into always passing a ticker.

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?

Three sentences, front-loaded with the metric list and the key routing hint. Little waste, though the mandatory-sounding tickers instruction is imprecise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema and full parameter descriptions, most burden is already carried, so the description mainly needs to state scope and routing. It does that adequately but omits the indicator enum's full set (8 metrics vs 4 listed) and gives no hint that lag/growth/trailing/standardize change the returned series shape.

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 coverage is 100%, so the baseline is 3; the description mostly restates schema content (comma-separated tickers, quarterly=true, start_date/end_date). It adds no meaning for the more complex parameters (lag, trailing, standardize, growth, limit) that remain schema-only.

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?

States a specific verb+resource: pre-computed liquidity ratios, and enumerates the concrete metrics (current, quick, cash ratio, working capital). It distinguishes itself from raw financial statements, though it doesn't differentiate from the sibling ratio families (efficiency, solvency, profitability) it sits alongside.

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?

"Use instead of raw financial statements" gives one clear routing rule, but with 26 siblings all being analysis families, there is no guidance for choosing liquidity over solvency or efficiency. Usage conditions like quarterly/date ranges are stated but framed as capabilities rather than selection criteria.

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

liquidity

Instructions

Input Schema

Output Schema

Schema Changelog

TDQS

Other Tools