Skip to main content
Glama
JerBouma

Finance Toolkit

by JerBouma

efficiency

Read-onlyIdempotent

Calculate asset turnover, inventory turnover, days sales outstanding, days payable outstanding, and cash conversion cycle from ticker data instead of raw statements.

Instructions

Pre-computed efficiency ratios (asset turnover, inventory turnover, days sales outstanding, days payable outstanding, cash conversion cycle). 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_days_of_inventory_outstanding, get_days_of_sales_outstanding, get_operating_cycle, get_days_of_accounts_payable_outstanding, get_cash_conversion_cycle, get_cash_conversion_efficiency, get_receivables_turnover, get_inventory_turnover_ratio, get_accounts_payables_turnover_ratio, get_sga_to_revenue_ratio, get_fixed_asset_turnover, get_asset_turnover_ratio, get_operating_ratio, get_research_and_development_ratio, get_selling_and_marketing_ratio, get_general_and_administrative_ratio, get_stock_based_compensation_ratio, get_deferred_revenue_ratio, get_working_capital_turnover_ratio.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lagNoNumber of periods to lag when computing growth rates.
daysNoNumber of calendar days used in day-count-based calculations.
growthNoReturn period-over-period growth rates instead of absolute values.
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.
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_days_of_inventory_outstanding",
      -  "get_days_of_sales_outstanding",
      -  "get_operating_cycle",
      -  "get_days_of_accounts_payable_outstanding",
      -  "get_cash_conversion_cycle",
      -  "get_cash_conversion_efficiency",
      -  "get_receivables_turnover",
      -  "get_inventory_turnover_ratio",
      -  "get_accounts_payables_turnover_ratio",
      -  "get_sga_to_revenue_ratio",
      -  "get_fixed_asset_turnover",
      -  "get_asset_turnover_ratio",
      -  "get_operating_ratio",
      -  "get_research_and_development_ratio",
      -  "get_selling_and_marketing_ratio",
      -  "get_general_and_administrative_ratio",
      -  "get_stock_based_compensation_ratio",
      -  "get_deferred_revenue_ratio"
      -]New value: +[
      +  "get_days_of_inventory_outstanding",
      +  "get_days_of_sales_outstanding",
      +  "get_operating_cycle",
      +  "get_days_of_accounts_payable_outstanding",
      +  "get_cash_conversion_cycle",
      +  "get_cash_conversion_efficiency",
      +  "get_receivables_turnover",
      +  "get_inventory_turnover_ratio",
      +  "get_accounts_payables_turnover_ratio",
      +  "get_sga_to_revenue_ratio",
      +  "get_fixed_asset_turnover",
      +  "get_asset_turnover_ratio",
      +  "get_operating_ratio",
      +  "get_research_and_development_ratio",
      +  "get_selling_and_marketing_ratio",
      +  "get_general_and_administrative_ratio",
      +  "get_stock_based_compensation_ratio",
      +  "get_deferred_revenue_ratio",
      +  "get_working_capital_turnover_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_days_of_inventory_outstanding",
      -  "get_days_of_sales_outstanding",
      -  "get_operating_cycle",
      -  "get_days_of_accounts_payable_outstanding",
      -  "get_cash_conversion_cycle",
      -  "get_cash_conversion_efficiency",
      -  "get_receivables_turnover",
      -  "get_inventory_turnover_ratio",
      -  "get_accounts_payables_turnover_ratio",
      -  "get_sga_to_revenue_ratio",
      -  "get_fixed_asset_turnover",
      -  "get_asset_turnover_ratio",
      -  "get_operating_ratio"
      -]New value: +[
      +  "get_days_of_inventory_outstanding",
      +  "get_days_of_sales_outstanding",
      +  "get_operating_cycle",
      +  "get_days_of_accounts_payable_outstanding",
      +  "get_cash_conversion_cycle",
      +  "get_cash_conversion_efficiency",
      +  "get_receivables_turnover",
      +  "get_inventory_turnover_ratio",
      +  "get_accounts_payables_turnover_ratio",
      +  "get_sga_to_revenue_ratio",
      +  "get_fixed_asset_turnover",
      +  "get_asset_turnover_ratio",
      +  "get_operating_ratio",
      +  "get_research_and_development_ratio",
      +  "get_selling_and_marketing_ratio",
      +  "get_general_and_administrative_ratio",
      +  "get_stock_based_compensation_ratio",
      +  "get_deferred_revenue_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

A3.6/5.0
Behavior3/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 operational context such as ticker formatting and indicator availability, but does not disclose rate limits, auth requirements, or other behavioral traits. It also states tickers are required despite the schema marking tickers optional, which may mislead.

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 description is front-loaded with purpose and key usage notes, which is good. However, the long list of available indicators duplicates the enum already present in the schema, bloating the description without adding new information.

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 rich input schema (100% coverage), output schema, and annotations, the description covers the core purpose, indicator selection, and main optional parameters sufficiently. The many advanced parameters are documented in the schema, so the description does not need to repeat them, though the ticker requirement inconsistency is a minor gap.

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 parameter meanings are already fully documented. The description mostly repeats enum values and comma-separated ticker syntax, though it does add a useful 'use instead of raw financial statements' framing. The claim that tickers are required conflicts with the schema and reduces added value.

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 names the resource category (pre-computed efficiency ratios) and gives concrete examples such as asset turnover and cash conversion cycle. It distinguishes itself from raw financial statements, but does not explicitly differentiate from sibling category tools like profitability or liquidity.

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?

It states a key use case: 'Use instead of raw financial statements,' and documents required ticker formatting and supported parameters like quarterly and start_date/end_date. It lacks explicit when-not guidance or comparisons to sibling ratio tools, but the intended context is clear.

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