Skip to main content
Glama

DCF + Owner Earnings + Damodaran intrinsic value

intrinsic_value
Read-only

Per-method intrinsic value per share (DCF on free cash flow, owner earnings, Damodaran two-stage), their equal-weight blend, Monte Carlo bounds and the implied gap to the current price, and the lead value the DeepValues apps headline (lead_method, lead_intrinsic_value, lead_upside_pct, values.lead_intrinsic_value_per_share): Owner Earnings, or the DCF and then Damodaran when Owner Earnings has no positive value. The blend is checked against the price before it is served: if it fails a check (not positive, more than 20x the price, a price older than five days, no price, or currency_consistent: statements left in a currency other than the USD price), the valuation fields are null, withheld is true, checks.failed names the check and the call is not charged. A value under 0.05x the price is served with the flag iv_far_below_price. A value built from statements converted to USD carries fx (from the filer's currency, to USD, rate, rate_date, rate_type) on values.intrinsic_value_per_share and each method input; currency_unverified in checks.flags means the statement currency is not known for this ticker, so the check did not run. A method with no value is null in methods, never 0, and methods_unavailable says why (code, family: negative_cash_flow, financial_company, withheld or missing_inputs, and the pipeline's reason). For a one-call answer with holders and a verdict, use /brief/{ticker}. (GET https://app.deepvalues.ai/api/v1/intrinsic-value/{ticker}, e.g. https://app.deepvalues.ai/api/v1/intrinsic-value/AAPL — 0.02 credits per call; works with no credentials up to 5 call(s)/day per address) Missing data? Call request_data.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "intrinsic_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesThe real ticker symbol, e.g. AAPL; share classes as BRK.B or BRK-B. Substitute it into the path (/fundamentals/AAPL), never the literal {ticker}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / ticker / description
      Added value: +"The real ticker symbol, e.g. AAPL; share classes as BRK.B or BRK-B. Substitute it into the path (/fundamentals/AAPL), never the literal {ticker}."
    • addedInput schema / properties / ticker / examples
      Added value: +[
      +  "AAPL"
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Far beyond the readOnly/openWorld annotations, it discloses the withholding logic (non-positive, >20x price, stale price, missing price, currency inconsistency), the resulting null fields with the call not charged, the `iv_far_below_price` flag, `fx` provenance and `currency_unverified` behavior, and why a method is null rather than 0.

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?

Every sentence carries real information, but the whole thing is one dense, parenthesis-laden run-on that is hard to scan; sub-bullets for withholding rules, flags and FX would preserve the content with far better structure.

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

Completeness5/5

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

For a tool with no output schema, this covers what gets returned, what null means, what flags appear on which fields, the cost model, and the credential-free quota. An agent has everything needed to call it and interpret the response.

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% for the single `ticker` parameter, so the schema already documents format and share-class handling. The description adds no ticker-specific semantics beyond what the schema states, so the baseline 3 applies.

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 opens with the exact resources computed – DCF on free cash flow, owner earnings, Damodaran two-stage, their blend, Monte Carlo bounds and the gap to price – then names the lead-value fields. An agent can distinguish this from fundamentals or verdict purely from the text.

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 routes agents explicitly: "For a one-call answer with holders and a verdict, use /brief/{ticker}", and gives cost (0.02 credits) plus credential-free limits (5 calls/day). It never states a when-not-to-use case beyond that single redirect, so it falls short of a full 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources