Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Generate Peer Comparables Workbook (xlsx)

generate_comps_xlsx

Render a peer comparables table into an Excel workbook. The Comps sheet is formatted as a named Excel Table (ValueinPeerComps) so the user gets one-click Insert Chart on any column — the cleanest workaround for not embedding chart objects server-side. Subject-row highlight makes side-by-side comparison instant. A Summary sheet adds subject vs peer-median deltas.

SERVER-TRUST: the ratios you pass are rendered as-supplied and are NOT re-derived by Valuein, so the workbook carries a visible 'figures supplied by caller, not verified by Valuein' watermark (response verification.status = 'unverified'). For authoritative numbers, source them from get_peer_comparables / get_financial_ratios first.

Pair with get_peer_comparables for a typical flow.

Tier: pro+.

Input Schema

Name	Required	Description
`notes`	No	Optional free-text note (≤500 chars) rendered on the Summary sheet.
`peers`	Yes	Peer companies to tabulate against the subject (1–50 rows); each row carries the peer's ticker, name, and comparable ratio values.
`subject_ticker`	Yes	Stock ticker symbol of the subject company the comps sheet is built around, e.g. AAPL.
`subject_company_name`	No	Optional display name for the subject company; falls back to the ticker if omitted.

Output 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. Comps ratios are rendered as supplied and are NOT re-derived by Valuein, so the workbook carries a visible 'figures supplied by caller' watermark. Pull authoritative ratios via get_peer_comparables / get_financial_ratios.
`expires_in_seconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedOutput schema / properties / _meta / properties / cost_usd / properties / basis / description

Previous value: -"payg_charge = real charge (agent-pay or your balance). payg_rate_card = indicative price, not billed."New value: +"payg_charge = real pay-per-call charge (a card or MPP payment through agent-pay). payg_rate_card = indicative price, not billed."

Changed2 schema fields changedOct 29, 2026

changedOutput schema / properties / _meta / properties / cost_usd / properties / basis / description

Previous value: -"payg_charge = real agent-pay charge. payg_rate_card = indicative price, not billed."New value: +"payg_charge = real charge (agent-pay or your balance). payg_rate_card = indicative price, not billed."

changedOutput schema / properties / _meta / properties / cost_usd / properties / billed / description

Previous value: -"true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value; your plan already covers this call for free."New value: +"true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value only: no charge was made for this call (it was within your plan)."

AddedOct 16, 2026
RemovedSep 29, 2026

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. Comps ratios are rendered as supplied and are NOT re-derived by Valuein, so the workbook carries a visible 'figures supplied by caller' watermark. Pull authoritative ratios via get_peer_comparables / get_financial_ratios.",
+  "properties": {
+    "note": {
+      "type": "string"
+    },
+    "status": {
+      "const": "unverified",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "note"
+  ],
+  "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"
```

Changed4 schema fields changedJun 3, 2026

addedInput schema / properties / notes / description

Added value: +"Optional free-text note (≤500 chars) rendered on the Summary sheet."

addedInput schema / properties / peers / description

Added value: +"Peer companies to tabulate against the subject (1–50 rows); each row carries the peer's ticker, name, and comparable ratio values."

addedInput schema / properties / subject_company_name / description

Added value: +"Optional display name for the subject company; falls back to the ticker if omitted."

addedInput schema / properties / subject_ticker / description

Added value: +"Stock ticker symbol of the subject company the comps sheet is built around, e.g. AAPL."

AddedMay 13, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the most important behavioral fact: inputs are rendered as-supplied and not re-derived, the workbook carries a visible unverified watermark, and response verification.status = 'unverified'. Also describes the artifact's structure (named Excel Table for one-click charts, subject-row highlight, Summary deltas), which an agent needs to write meaningful feedback about the output.

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?

Front-loaded with the core action, followed by labeled SERVER-TRUST and Pair-with guidance — efficient structure. Slightly padded with rationale prose ('the cleanest workaround for not embedding chart objects server-side') that serves the agent little, and the Tier line is appended without context for how the agent should act on it.

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 and the description still adds the non-obvious parts the schema can't convey: watermarking, verification status, sheet layout, and the sourcing prerequisite. Nearly complete, though it doesn't say how the workbook is returned to the caller (link vs artifact reference) or whether repeated calls overwrite or create new artifacts, which matters given idempotentHint=false.

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 coverage is already 100%, so the baseline is 3; the description adds real meaning by explaining that the peer ratio values are treated as caller-supplied figures rather than recomputed, which changes how an agent should populate them. It doesn't say anything further about individual fields (notes placement, min/max peers), which the schema already covers.

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?

States a concrete verb + resource: render a peer comparables table into an Excel workbook, plus what the artifact contains (Comps sheet, Summary sheet). This clearly distinguishes it from sibling generators like generate_dcf_xlsx / generate_lbo_xlsx and from the data-retrieval sibling get_peer_comparables, which it explicitly names as the upstream.

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?

Gives concrete routing guidance: use get_peer_comparables / get_financial_ratios first for authoritative numbers, and 'Pair with get_peer_comparables for a typical flow.' It also states the tier gate (pro+). Missing an explicit 'when not to use me' (e.g. choosing this over an inline table), so it stops short of a 5.

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.