Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Compute Forward DCF

compute_dcf

Read-onlyIdempotent

Forward discounted-cash-flow valuation (two-stage Gordon-growth model): caller provides growth + WACC + terminal assumptions, returns per-share intrinsic value (value_per_share_cents, cents USD) + 5×5 sensitivity grid. Pulls FCF base + net debt + shares from R2; caller can override any field. Definitions (consistent with get_financial_ratios / get_capital_allocation_profile): FCF base = operating_cash_flow − capex (absolute USD); net_debt = total_debt − (cash + short-term investments). Shares resolve via a fallback chain (valuation row → fact CommonSharesOutstanding → net_income/eps_diluted), reported as result.shares_source. The pulled inputs are echoed in result.inputs_echo with their source lineage so the valuation is reproducible and traceable. A null value_per_share_cents means the model is degenerate (e.g. WACC ≤ terminal growth, or FCF base ≤ 0) or a required input was unavailable — it is NOT a zero valuation; the reason field explains. Use the returned figures exactly. Use this when you want to drive the assumptions yourself; for the pipeline's pre-computed DCF/DDM value and inputs (no assumptions needed) use get_valuation_metrics instead. Does NOT persist a report — use create_report (report_type:'reverse_dcf') for that.

fcf_source (default "trend"): "trend" compounds a single FCF base by stage1_growth_rate every year (the original behavior, unchanged). "three_statement" instead runs a full linked Income Statement / Balance Sheet / Cash Flow projection (project_three_statement's engine) and feeds its year-by-year FCF stream into the same PV math — stage1_growth_rate is then ignored (kept for echo only) because revenue growth + margins drive FCF instead of a flat compounding rate. The projection detail (including per-year tie_out_ok) is returned in three_statement_detail when used. Tier: sp500+.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`wacc`	No	Discount rate. Default 0.09.
`ticker`	Yes	Stock ticker symbol of the company to value, e.g. AAPL, MSFT, BRK.B.
`as_of_date`	No	Point-in-time cutoff (YYYY-MM-DD) for the auto-pulled inputs. Fundamentals are filtered by SEC accepted_at (strict PIT); valuation.parquet inputs are best-effort PIT (filtered by created_at, its accepted_at proxy — no SEC acceptance timestamp exists for pipeline-computed valuations). Omit to use the latest knowable inputs.
`fcf_source`	No	"trend" (default): compound fcf_base by stage1_growth_rate every year (unchanged original behavior). "three_statement": derive the FCF stream from a full linked 3-statement projection instead — see the tool description for details.	trend
`stage1_years`	No	Number of explicit high-growth projection years before the terminal stage (3–15). Defaults to 5.
`shares_override`	No	Override shares outstanding. Leave unset to use R2-derived.
`fcf_base_override`	No	Override the auto-pulled FCF base (USD). Leave unset to use R2-derived.
`stage1_growth_rate`	Yes	Stage-1 FCF growth rate (e.g. 0.12 = 12%/yr).
`terminal_growth_rate`	No	Long-run growth. Default 0.025.
`three_statement_assumptions`	No	Only used when fcf_source is "three_statement". Overrides for the underlying projection; unset fields use project_three_statement's defaults.

Output Schema

TableJSON Schema

Name	Required	Description
`_meta`	Yes	Provenance envelope — data lineage for every MCP response
`result`	Yes
`ticker`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 18, 2026

changedOutput schema / properties / _meta / properties / fundamentals_as_of / description

Previous value: -"ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt. Use THIS — not `last_updated` — when telling a user how current the fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to."New value: +"ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt in bulk. Use THIS — not `last_updated` — when telling a user how current the cross-sectional fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to. It is a floor for a single filer, not a ceiling: a filer with a live partition receives its filing, facts and ratios intraday (minutes after EDGAR dissemination), so an entity-scoped read may carry a filing newer than this; cross-sectional ranks (factor scores, earnings signals) refresh with the weekly bulk export."

Changed2 schema fields changedJul 25, 2026

addedOutput schema / properties / _meta / properties / fundamentals_as_of

Added value: +{
+  "description": "ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt. Use THIS — not `last_updated` — when telling a user how current the fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to.",
+  "type": "string"
+}

addedOutput schema / properties / _meta / properties / price_as_of

Added value: +{
+  "description": "ISO timestamp when the price surfaces were last refreshed.",
+  "type": "string"
+}

Changed2 schema fields changedJul 9, 2026

addedInput schema / properties / fcf_source

Added value: +{
+  "default": "trend",
+  "description": "\"trend\" (default): compound fcf_base by stage1_growth_rate every year (unchanged original behavior). \"three_statement\": derive the FCF stream from a full linked 3-statement projection instead — see the tool description for details.",
+  "enum": [
+    "trend",
+    "three_statement"
+  ],
+  "type": "string"
+}

addedInput schema / properties / three_statement_assumptions

Added value: +{
+  "additionalProperties": false,
+  "description": "Only used when fcf_source is \"three_statement\". Overrides for the underlying projection; unset fields use project_three_statement's defaults.",
+  "properties": {
+    "cash_sweep_pct": {
+      "description": "Default 0.",
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    "dividend_payout_pct": {
+      "description": "Default 0.",
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    "interest_rate_on_debt": {
+      "description": "Default 0.06.",
+      "maximum": 0.5,
+      "minimum": 0,
+      "type": "number"
+    },
+    "tax_rate": {
+      "description": "Default 0.21.",
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedJul 7, 2026

addedOutput schema / properties / _meta / properties / cost_usd

Added value: +{
+  "additionalProperties": false,
+  "description": "Per-call cost transparency. Omitted for subscription-only tools that have no PAYG-equivalent price.",
+  "properties": {
+    "amount_usd": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "basis": {
+      "description": "payg_charge = real agent-pay charge. payg_rate_card = indicative price, not billed.",
+      "enum": [
+        "payg_charge",
+        "payg_rate_card"
+      ],
+      "type": "string"
+    },
+    "billed": {
+      "description": "true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value; your plan already covers this call for free.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "amount_usd",
+    "billed",
+    "basis"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / _meta / properties / latency_ms

Added value: +{
+  "description": "Wall-clock milliseconds this tool call took, measured server-side around the handler.",
+  "minimum": 0,
+  "type": "integer"
+}

Changed1 schema field changedJun 18, 2026
- addedOutput schema / properties / _meta / properties / pit_safe / description
```
Added value: +"true iff a zero-look-ahead point-in-time cut was applied to every returned figure"
```

Changed1 schema field changedJun 5, 2026

addedInput schema / properties / as_of_date

Added value: +{
+  "description": "Point-in-time cutoff (YYYY-MM-DD) for the auto-pulled inputs. Fundamentals are filtered by SEC accepted_at (strict PIT); valuation.parquet inputs are best-effort PIT (filtered by created_at, its accepted_at proxy — no SEC acceptance timestamp exists for pipeline-computed valuations). Omit to use the latest knowable inputs.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

Changed2 schema fields changedJun 3, 2026

addedInput schema / properties / stage1_years / description

Added value: +"Number of explicit high-growth projection years before the terminal stage (3–15). Defaults to 5."

addedInput schema / properties / ticker / description

Added value: +"Stock ticker symbol of the company to value, e.g. AAPL, MSFT, BRK.B."

AddedMay 12, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Even though annotations already mark it readOnly/idempotent/non-destructive, the description adds critical behavior: R2-derived inputs with override semantics, share fallback chain, inputs_echo lineage, degenerate-model null semantics with reason field, and the fcf_source mode behavior. No contradiction with annotations.

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?

Dense and logically organized, front-loading the core result and caveats before mode details. Not maximally concise because some points (overrides, echo) are also present in schema descriptions, but every paragraph earns its place given the tool's complexity.

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 10-parameter tool with nested assumptions and an output schema, this is complete: it explains output fields, null semantics, source lineage, definitions, mode alternatives, and interactions with sibling tools. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant meaning beyond the schema: it defines FCF base and net debt consistently with sibling tools, explains fcf_source 'trend' vs 'three_statement' behavior, clarifies that stage1_growth_rate is ignored in three_statement mode, and details shares resolution and three_statement_assumptions usage.

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?

Description opens with a specific verb and resource: 'Forward discounted-cash-flow valuation (two-stage Gordon-growth model)' and states it returns per-share intrinsic value plus a sensitivity grid. It clearly differentiates from siblings by naming get_valuation_metrics, compute_lbo, compute_accretion_dilution, and create_report.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent when to use it ('Use this when you want to drive the assumptions yourself') and when not to ('for the pipeline's pre-computed DCF/DDM value ... use get_valuation_metrics instead'). Also clarifies it does not persist a report and routes to create_report with report_type:'reverse_dcf'.

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

All Valuein — SEC EDGAR Fundamentals & Smart-Money Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.