Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Project Linked Three-Statement Model

project_three_statement

Read-onlyIdempotent

Linked forward Income Statement / Balance Sheet / Cash Flow projection, seeded from the company's latest historical annual period. The balance sheet ties out (assets == liabilities + equity) EVERY projected year by algebraic construction — each year's tie_out_ok field is a live correctness check, not decoration. Interest is computed on beginning-of-period debt balances (no circular cash-sweep/revolver solve — deterministic by design). Gross margin, operating margin, and the combined D&A + working-capital adjustment are held at the seed period's ratio-of-revenue unless overridden; interest_rate_on_debt and tax_rate are ASSUMPTIONS (no historical InterestExpense concept exists in the dataset). Every simplification is listed in the response caveats[] — read them before presenting this as a precise forecast. Returns a fcf_stream usable directly as compute_dcf's fcf_source:"three_statement" input. Tier: sp500+.

Input Schema

TableJSON Schema

Name	Required	Description
`years`	No	Projection horizon in years (1-15). Defaults to 5.
`ticker`	Yes	Stock ticker symbol, e.g. AAPL, MSFT, BRK.B.
`tax_rate`	No	Effective tax rate on positive pretax income. Default 0.21 (US statutory).
`as_of_date`	No	Point-in-time cutoff (YYYY-MM-DD) for the seed period. Omit to use the latest knowable annual period.
`cash_sweep_pct`	No	Fraction (0-1) of each year's free cash flow swept to debt paydown. Default 0 (going-concern; use ~1.0 for an LBO-style paydown).
`dividend_payout_pct`	No	Fraction (0-1) of net income paid out as dividends each year. Default 0.
`new_debt_draw_year1`	No	New debt drawn at year 1 only (absolute USD) — e.g. acquisition financing. Default 0.
`revenue_growth_rate`	Yes	Flat annual revenue growth rate applied every year (e.g. 0.08 = 8%/yr).
`interest_rate_on_debt`	No	Annual interest rate on beginning-of-period debt. Assumption — default 0.06.
`new_equity_draw_year1`	No	New equity contributed at year 1 only (absolute USD) — hits cash + equity symmetrically. Default 0.
`gross_margin_pct_override`	No	Override the seed period's gross margin (held flat across all years). Leave unset to use the historical ratio.
`capex_pct_of_revenue_override`	No	Override the seed period's capex-as-%-of-revenue ratio. Leave unset to use the historical ratio.
`operating_margin_pct_override`	No	Override the seed period's operating margin. Leave unset to use the historical ratio.

Output Schema

TableJSON Schema

Name	Required	Description
`_meta`	Yes	Provenance envelope — data lineage for every MCP response
`result`	Yes
`ticker`	Yes
`seed_period_end`	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"
+}

AddedJul 9, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent, but the description adds substantial behavioral depth: balance-sheet tie-out is 'a live correctness check, not decoration', interest uses beginning-of-period debt with 'no circular cash-sweep/revolver solve', margins and adjustments are ratcheted from the seed period unless overridden, and 'caveats[]' must be read before presenting results. This goes well beyond the safety hints and gives the agent a realistic model of how the tool behaves.

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?

The description is longer than the ideal two-liner, but every sentence carries a unique, operationally relevant fact: projection scope, tie-out verification, interest calculation method, assumption defaults, caveat requirement, DCF integration, and tier restriction. It is front-loaded with the core purpose and proceeds logically without fluff.

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?

Given the 13-parameter complexity alert, the output schema, and annotations, the description is complete. It covers what the model produces, how it handles assumptions, where to find caveats, and how the output connects to compute_dcf. The only minor omission would be explicit guidance on interpreting output fields, but the output schema already provides that.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds real value by clarifying that tax_rate and interest_rate_on_debt are assumptions (no historical InterestExpense exists) and by explaining that gross/operating margins and D&A + working-capital adjustments default to seed-period ratios unless override parameters are set. This helps the agent reason about which parameters to touch and what their absence means.

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 a specific verb and resource: 'Linked forward Income Statement / Balance Sheet / Cash Flow projection', and immediately grounds it with the seed source and output integration ('fcf_stream usable directly as compute_dcf'). It clearly differentiates from siblings like compute_lbo or compute_dcf by positioning itself as the input-generating projection model.

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?

Usage is implied through the cross-tool note that the returned fcf_stream feeds compute_dcf, and the 'Tier: sp500+' access constraint. However, there is no explicit when-to-use-versus-alternatives guidance (e.g., when to choose this over compute_lbo or generate_dcf_xlsx), so the agent must infer the appropriate context from the name and integration hint.

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.