Skip to main content
Glama
JerBouma

Finance Toolkit

valuation

Read-onlyIdempotent

Calculate pre-computed valuation ratios like P/E, EV/EBITDA, P/B, and dividend yield for one or more tickers, so you can assess a stock's value without parsing raw financial statements.

Instructions

Pre-computed valuation ratios (P/E, EPS, EV/EBITDA, EV/EBIT, P/B, P/S, PEG, dividend yield, FCF yield, market cap, forward P/E, forward PEG). Requires tickers='AAPL' — use comma-separated values for multiple tickers. Use instead of raw financial statements. Supports quarterly=true and start_date/end_date. get_forward_price_earnings_ratio and get_forward_price_earnings_growth_ratio additionally require a Premium FMP subscription and are fetched on first use only.

Input Schema

NameRequiredDescriptionDefault
lagNoNumber of periods to lag when computing growth rates.
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.
dilutedNoFor get_earnings_per_share: Whether to use diluted earnings per share. For get_revenue_per_share, get_price_to_earnings_ratio, get_price_to_earnings_growth_ratio, get_book_value_per_share, get_price_to_book_ratio, get_interest_debt_per_share, get_capex_per_share, get_earnings_yield, get_weighted_dividend_yield, get_price_to_cash_flow_ratio, get_price_to_free_cash_flow_ratio, get_market_cap, get_enterprise_value, get_ev_to_sales_ratio, get_ev_to_ebit, get_ev_to_ebitda_ratio, get_ev_to_operating_cashflow_ratio, get_ev_to_free_cash_flow_ratio, get_buyback_yield, get_shareholder_yield, get_price_to_sales_ratio: Whether to use diluted shares in the calculation.
tickersNoComma-separated ticker symbols, e.g. 'AAPL,MSFT,GOOGL'.
end_dateNoEnd of the date range in YYYY-MM-DD format.2026-10-27
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.
show_dailyNoFor get_price_to_earnings_ratio, get_price_to_book_ratio, get_earnings_yield, get_weighted_dividend_yield, get_price_to_cash_flow_ratio, get_price_to_free_cash_flow_ratio, get_market_cap, get_enterprise_value, get_ev_to_sales_ratio, get_ev_to_ebit, get_ev_to_ebitda_ratio, get_ev_to_operating_cashflow_ratio, get_ev_to_free_cash_flow_ratio, get_price_to_sales_ratio: Whether to show daily values: the close of each trading day against the statement figures of the latest period that has ended on or before that day, so no figures are used before their period closes. For get_dividend_yield: Whether to show daily values: the close of each trading day against the dividends paid in the 365 calendar days up to that day (or the `trailing` periods in days). Days less than one window after the first price are NaN.
start_dateNoStart of the date range in YYYY-MM-DD format.2021-10-28
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
include_dividendsNoFor get_earnings_per_share: Whether to deduct the preferred dividends paid from net income. For get_price_to_earnings_ratio, get_earnings_yield: Whether to deduct preferred dividends from net income. For get_price_to_earnings_growth_ratio: Whether to deduct preferred dividends from net income, in both the P/E and the EPS growth (not in the EBITDA growth).
use_ebitda_growth_rateNoWhether to use EBITDA growth rate for the calculation.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.3.0
    • changedInput schema / properties / end_date / default
      Previous value: -"2026-10-14"New value: +"2026-10-27"
    • changedInput schema / properties / include_dividends / description
      Previous value: -"For get_earnings_per_share: Whether to include dividends in the EPS calculation. For get_price_to_earnings_ratio, get_price_to_earnings_growth_ratio, get_earnings_yield: Whether to include dividends in the calculation."New value: +"For get_earnings_per_share: Whether to deduct the preferred dividends paid from net income. For get_price_to_earnings_ratio, get_earnings_yield: Whether to deduct preferred dividends from net income. For get_price_to_earnings_growth_ratio: Whether to deduct preferred dividends from net income, in both the P/E and the EPS growth (not in the EBITDA growth)."
    • changedInput schema / properties / show_daily / description
      Previous value: -"Whether to show daily data."New value: +"For get_price_to_earnings_ratio, get_price_to_book_ratio, get_earnings_yield, get_weighted_dividend_yield, get_price_to_cash_flow_ratio, get_price_to_free_cash_flow_ratio, get_market_cap, get_enterprise_value, get_ev_to_sales_ratio, get_ev_to_ebit, get_ev_to_ebitda_ratio, get_ev_to_operating_cashflow_ratio, get_ev_to_free_cash_flow_ratio, get_price_to_sales_ratio: Whether to show daily values: the close of each trading day against the statement figures of the latest period that has ended on or before that day, so no figures are used before their period closes. For get_dividend_yield: Whether to show daily values: the close of each trading day against the dividends paid in the 365 calendar days up to that day (or the `trailing` periods in days). Days less than one window after the first price are NaN."
    • changedInput schema / properties / start_date / default
      Previous value: -"2021-10-15"New value: +"2021-10-28"
  2. Changed28 schema fields changedv2.2.3
    • removedInput schema / properties / benchmark_ticker / title
      Removed value: -"Benchmark Ticker"
    • changedInput schema / properties / diluted / description
      Previous value: -"Value for diluted."New value: +"For get_earnings_per_share: Whether to use diluted earnings per share. For get_revenue_per_share, get_price_to_earnings_ratio, get_price_to_earnings_growth_ratio, get_book_value_per_share, get_price_to_book_ratio, get_interest_debt_per_share, get_capex_per_share, get_earnings_yield, get_weighted_dividend_yield, get_price_to_cash_flow_ratio, get_price_to_free_cash_flow_ratio, get_market_cap, get_enterprise_value, get_ev_to_sales_ratio, get_ev_to_ebit, get_ev_to_ebitda_ratio, get_ev_to_operating_cashflow_ratio, get_ev_to_free_cash_flow_ratio, get_buyback_yield, get_shareholder_yield, get_price_to_sales_ratio: Whether to use diluted shares in the calculation."
    • removedInput schema / properties / diluted / title
      Removed value: -"Diluted"
    • 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 / include_dividends / description
      Previous value: -"Value for include_dividends."New value: +"For get_earnings_per_share: Whether to include dividends in the EPS calculation. For get_price_to_earnings_ratio, get_price_to_earnings_growth_ratio, get_earnings_yield: Whether to include dividends in the calculation."
    • removedInput schema / properties / include_dividends / title
      Removed value: -"Include Dividends"
    • 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"
    • changedInput schema / properties / show_daily / description
      Previous value: -"Value for show_daily."New value: +"Whether to show daily data."
    • removedInput schema / properties / show_daily / title
      Removed value: -"Show Daily"
    • 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"
    • changedInput schema / properties / use_ebitda_growth_rate / description
      Previous value: -"Value for use_ebitda_growth_rate."New value: +"Whether to use EBITDA growth rate for the calculation."
    • removedInput schema / properties / use_ebitda_growth_rate / title
      Removed value: -"Use Ebitda Growth Rate"
    • removedInput schema / title
      Removed value: -"valuationArguments"
  3. 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"
  4. 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_earnings_per_share",
      -  "get_revenue_per_share",
      -  "get_price_to_earnings_ratio",
      -  "get_price_to_earnings_growth_ratio",
      -  "get_forward_price_earnings_ratio",
      -  "get_forward_price_earnings_growth_ratio",
      -  "get_book_value_per_share",
      -  "get_price_to_book_ratio",
      -  "get_interest_debt_per_share",
      -  "get_capex_per_share",
      -  "get_earnings_yield",
      -  "get_dividend_payout_ratio",
      -  "get_dividend_yield",
      -  "get_weighted_dividend_yield",
      -  "get_price_to_cash_flow_ratio",
      -  "get_price_to_free_cash_flow_ratio",
      -  "get_market_cap",
      -  "get_enterprise_value",
      -  "get_ev_to_sales_ratio",
      -  "get_ev_to_ebit",
      -  "get_ev_to_ebitda_ratio",
      -  "get_ev_to_operating_cashflow_ratio",
      -  "get_tangible_asset_value",
      -  "get_net_current_asset_value",
      -  "get_ev_to_free_cash_flow_ratio",
      -  "get_buyback_yield",
      -  "get_shareholder_yield",
      -  "get_sbc_adjusted_free_cash_flow"
      -]New value: +[
      +  "get_earnings_per_share",
      +  "get_revenue_per_share",
      +  "get_price_to_earnings_ratio",
      +  "get_price_to_earnings_growth_ratio",
      +  "get_forward_price_earnings_ratio",
      +  "get_forward_price_earnings_growth_ratio",
      +  "get_book_value_per_share",
      +  "get_price_to_book_ratio",
      +  "get_interest_debt_per_share",
      +  "get_capex_per_share",
      +  "get_earnings_yield",
      +  "get_dividend_payout_ratio",
      +  "get_dividend_yield",
      +  "get_weighted_dividend_yield",
      +  "get_price_to_cash_flow_ratio",
      +  "get_price_to_free_cash_flow_ratio",
      +  "get_market_cap",
      +  "get_enterprise_value",
      +  "get_ev_to_sales_ratio",
      +  "get_ev_to_ebit",
      +  "get_ev_to_ebitda_ratio",
      +  "get_ev_to_operating_cashflow_ratio",
      +  "get_tangible_asset_value",
      +  "get_net_current_asset_value",
      +  "get_ev_to_free_cash_flow_ratio",
      +  "get_buyback_yield",
      +  "get_shareholder_yield",
      +  "get_sbc_adjusted_free_cash_flow",
      +  "get_price_to_sales_ratio",
      +  "get_reinvestment_rate"
      +]
    • changedInput schema / properties / start_date / default
      Previous value: -"2021-07-15"New value: +"2021-08-20"
  5. 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_earnings_per_share",
      -  "get_revenue_per_share",
      -  "get_price_to_earnings_ratio",
      -  "get_price_to_earnings_growth_ratio",
      -  "get_book_value_per_share",
      -  "get_price_to_book_ratio",
      -  "get_interest_debt_per_share",
      -  "get_capex_per_share",
      -  "get_earnings_yield",
      -  "get_dividend_payout_ratio",
      -  "get_dividend_yield",
      -  "get_weighted_dividend_yield",
      -  "get_price_to_cash_flow_ratio",
      -  "get_price_to_free_cash_flow_ratio",
      -  "get_market_cap",
      -  "get_enterprise_value",
      -  "get_ev_to_sales_ratio",
      -  "get_ev_to_ebit",
      -  "get_ev_to_ebitda_ratio",
      -  "get_ev_to_operating_cashflow_ratio",
      -  "get_tangible_asset_value",
      -  "get_net_current_asset_value"
      -]New value: +[
      +  "get_earnings_per_share",
      +  "get_revenue_per_share",
      +  "get_price_to_earnings_ratio",
      +  "get_price_to_earnings_growth_ratio",
      +  "get_forward_price_earnings_ratio",
      +  "get_forward_price_earnings_growth_ratio",
      +  "get_book_value_per_share",
      +  "get_price_to_book_ratio",
      +  "get_interest_debt_per_share",
      +  "get_capex_per_share",
      +  "get_earnings_yield",
      +  "get_dividend_payout_ratio",
      +  "get_dividend_yield",
      +  "get_weighted_dividend_yield",
      +  "get_price_to_cash_flow_ratio",
      +  "get_price_to_free_cash_flow_ratio",
      +  "get_market_cap",
      +  "get_enterprise_value",
      +  "get_ev_to_sales_ratio",
      +  "get_ev_to_ebit",
      +  "get_ev_to_ebitda_ratio",
      +  "get_ev_to_operating_cashflow_ratio",
      +  "get_tangible_asset_value",
      +  "get_net_current_asset_value",
      +  "get_ev_to_free_cash_flow_ratio",
      +  "get_buyback_yield",
      +  "get_shareholder_yield",
      +  "get_sbc_adjusted_free_cash_flow"
      +]
    • 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."
  6. 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"
  7. 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"
  8. 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"
  9. Addedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Goes beyond the readOnly/idempotent annotations by disclosing that two indicators require a Premium FMP subscription and are fetched only on first use — real operational constraints an agent would otherwise hit blind. It still omits rate limits and how large multi-ticker responses behave.

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?

Three sentences, front-loaded with the resource and metric list, then the required input, then the routing rule and edge caveats. The long parenthetical list is dense but every clause maps to a distinct call decision.

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?

An output schema exists, so return values need no explanation, and the description supplies the critical missing piece — that tickers must actually be supplied despite being optional in the schema. Remaining gaps (behavior of growth, trailing, limit) are adequately documented in the schema itself.

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 per-parameter detail is already carried by the schema and baseline 3 applies. The description only reinforces tickers formatting and the quarterly/date-range toggles, plus the Premium caveat; it adds nothing about the 15 non-required tuning params like lag, trailing, or standardize.

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?

Opens with a specific resource ('Pre-computed valuation ratios') and enumerates the exact metrics returned, so the agent knows this is a ratios endpoint rather than a statement endpoint. It is distinguishable from siblings like efficiency/liquidity/solvency by the listed metric families, but it never names those siblings explicitly.

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. However, it doesn't say when to prefer the sibling category tools, and the indicator schema points at search_metrics as the discovery path while the description stays silent about that relationship.

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