Skip to main content
Glama
JerBouma

Finance Toolkit

efficiency

Read-onlyIdempotent

Fetch pre-computed asset turnover, inventory turnover, DSO, DPO, and cash conversion cycle ratios for one or more tickers instead of raw financial 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.

Input Schema

NameRequiredDescriptionDefault
lagNoNumber of periods to lag when computing growth rates.
daysNoNumber of calendar days used in day-count-based calculations.
limitNoThe 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.
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-14
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, one of the listed values. Required — search_metrics finds the indicator (and its tool) for a metric by name.
quarterlyNoReturn quarterly data instead of annual when True.
start_dateNoStart of the date range in YYYY-MM-DD format.2021-10-15
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

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed21 schema fields changedv2.2.3
    • 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: -"efficiencyArguments"
  2. 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"
  3. 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"
  4. 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."
  5. 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"
  6. 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"
  7. 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"
  8. 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 structurally. The description adds that results are pre-computed (no client-side calculation) and that tickers is effectively required despite the empty default, but it says nothing about output shape, date defaults, or data recency.

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?

Four short sentences, purpose front-loaded, no filler. The ticker-format sentence partially repeats the schema's own tickers description, which is the only redundancy.

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?

Output schema and annotations exist, so return values and safety need not be explained. However, for a 13-parameter tool the description never mentions the required 'indicator' argument (one of 19 metrics) or routing via search_metrics/search_metric_categories, which is the single most important thing an agent must decide before calling.

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% across all 13 parameters, so the baseline is 3. The description only restates tickers format plus quarterly and start_date/end_date, adding no meaning beyond the schema's own parameter docs.

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 gives a specific resource ('Pre-computed efficiency ratios') and enumerates five representative metrics (asset turnover, inventory turnover, DSO, DPO, cash conversion cycle), which lets an agent distinguish it from category siblings like profitability or solvency. It does not explicitly name a sibling, so it stops short of the top tier.

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?

Gives concrete usage context: the tool is pre-computed, requires at least one ticker, accepts comma-separated multi-ticker input, and should be preferred over raw financial statements. No explicit 'when not to use' or pointer to sibling category tools, so it is clear context without exclusions.

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