Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Generate DCF Workbook (xlsx)

generate_dcf_xlsx

Render a forward DCF result into a professional Excel workbook (Summary + 5×5 Sensitivity heatmap + Inputs sheet). Native conditional formatting — no chart images needed. Returns a 15-minute presigned R2 download URL.

SERVER-TRUST: the DCF is re-derived in-Worker from the supplied inputs_echo (the math is pure + deterministic) and the workbook renders Valuein's recomputed figures — never the caller's claimed values. If the claimed figures disagree, the workbook is still produced but stamped with a visible correction banner and the response verification.status is 'corrected'. A fabricated per-share value can never appear as Valuein-authoritative.

Pair with compute_dcf for a typical analyst flow: agent calls compute_dcf({ticker, ...}), then passes the structured result straight to generate_dcf_xlsx({ticker, dcf_result, ...}) to materialise a shareable file.

Tier: pro+.

Input Schema

TableJSON Schema

Name	Required	Description
`ticker`	Yes	Stock ticker symbol of the company the DCF workbook is built for, e.g. AAPL.
`dcf_result`	Yes	Structured DCF result — typically the `result` field returned by `compute_dcf`.
`company_name`	No	Optional — surfaces on the cover row. Falls back to ticker only.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes
`_meta`	Yes	Provenance envelope — data lineage for every MCP response
`r2_key`	Yes
`filename`	Yes
`expires_at`	Yes
`size_bytes`	Yes
`content_type`	Yes
`verification`	Yes	Server-trust record. status='verified' when the caller's figures matched the server re-derivation; 'corrected' when they did not (the workbook shows the SERVER figures + a banner). `mismatches` lists every field that disagreed.
`expires_in_seconds`	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 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"
+}

Changed2 schema fields changedJun 19, 2026

addedOutput schema / properties / verification

Added value: +{
+  "additionalProperties": false,
+  "description": "Server-trust record. status='verified' when the caller's figures matched the server re-derivation; 'corrected' when they did not (the workbook shows the SERVER figures + a banner). `mismatches` lists every field that disagreed.",
+  "properties": {
+    "mismatches": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "claimed": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "derived": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "field": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "field",
+          "claimed",
+          "derived"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "note": {
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "verified",
+        "corrected"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "note",
+    "mismatches"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "_meta",
-  "url",
-  "r2_key",
-  "filename",
-  "content_type",
-  "size_bytes",
-  "expires_in_seconds",
-  "expires_at"
-]New value: +[
+  "_meta",
+  "url",
+  "r2_key",
+  "filename",
+  "content_type",
+  "size_bytes",
+  "expires_in_seconds",
+  "expires_at",
+  "verification"
+]

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"
```

Changed3 schema fields changedJun 5, 2026

removedInput schema / properties / dcf_result / properties / inputs_echo / properties / fcf_base
```
Removed value: -{
-  "type": "number"
-}
```
addedInput schema / properties / dcf_result / properties / inputs_echo / properties / fcf_base_total_usd
```
Added value: +{
+  "type": "number"
+}
```

changedInput schema / properties / dcf_result / properties / inputs_echo / required

Previous value: -[
-  "fcf_base",
-  "shares_outstanding",
-  "net_debt",
-  "stage1_growth_rate",
-  "wacc",
-  "terminal_growth_rate",
-  "stage1_years"
-]New value: +[
+  "fcf_base_total_usd",
+  "shares_outstanding",
+  "net_debt",
+  "stage1_growth_rate",
+  "wacc",
+  "terminal_growth_rate",
+  "stage1_years"
+]

Changed1 schema field changedJun 3, 2026

addedInput schema / properties / ticker / description

Added value: +"Stock ticker symbol of the company the DCF workbook is built for, e.g. AAPL."

AddedMay 13, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations are all false hints, so the description carries full behavioral disclosure. It richly explains that the DCF is re-derived from inputs_echo, that caller-claimed values are never treated as authoritative, that a correction banner appears on disagreement, and that verification.status may be 'corrected'. It also reveals the presigned URL timeout and native formatting — far beyond what annotations provide.

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 minimal but every section earns its place: purpose, trust model, and pairing flow. It is front-loaded with the deliverable and features. The SERVER-TRUST section is clearly labeled and the pairing paragraph is actionable. Slight verbosity in the trust explanation prevents a 5.

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 nested objects and an output schema, the description covers all essential agent-facing concerns: deliverable structure, server-side re-derivation, correction behavior, URL expiry, and the canonical pairing with compute_dcf. 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.

Parameters3/5

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

Schema description coverage is 100% and the schema already describes ticker, dcf_result, and company_name, including that dcf_result is typically the result field from compute_dcf. The tool description adds some context (e.g., inputs_echo role in re-derivation) but does not materially extend parameter semantics beyond the schema, so a baseline of 3 is appropriate.

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: 'Render a forward DCF result into a professional Excel workbook' and enumerates exact contents (Summary + 5×5 Sensitivity heatmap + Inputs sheet). It clearly distinguishes this from sibling xlsx generators like generate_comps_xlsx and generate_lbo_xlsx by focusing on DCF output.

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?

The description gives an explicit usage flow: 'Pair with compute_dcf for a typical analyst flow: agent calls compute_dcf({ticker, ...}), then passes the structured result straight to generate_dcf_xlsx({ticker, dcf_result, ...})'. This clearly states when to use the tool, though it does not explicitly enumerate when not to use it (e.g., for comps or LBO).

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.