Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Render Report Download URL

render_report

Idempotent

Return a 15-minute presigned download URL for a report in the requested binary format.

format=md presigns the cached markdown — instant, no compute. format=docx and format=pdf return the SAME branded research-note design in the two media: a masthead-first page 1 (Valuein letterhead — brand rule, wordmark, 'EQUITY RESEARCH' kicker + date), the ticker eyebrow and title, the named analyst's byline, then the body (abstract, sections with full markdown incl. GFM tables, citations table with clickable SEC EDGAR links) and a running footer (ticker, 'Built on Valuein · valuein.biz', page N of M, one disclosure line). The PDF embeds the Geist brand faces with figures set in tabular mono. Binary renders are cached in R2 after first build so repeat downloads are instant; pass force_regenerate: true to bust the cache (e.g. right after update_report).

Tier gate mirrors get_report: authors always see their own reports; non-authors below the report's required tier get an upgrade prompt.

Input Schema

TableJSON Schema

Name	Required	Description
`format`	Yes	md = raw markdown (the same body the editor renders). docx = branded Word document; pdf = the same branded research-note design as a shareable PDF (Geist faces embedded, clickable citation links).
`report_id`	Yes	Id from create_report or list_my_reports.
`author_name`	No	Display name of the report's author, shown as a named byline ('By {name}') on the masthead — the way a real research note credits an analyst. Omit to show 'Valuein Research'. Only affects the binary formats; ignored on a cache hit (the cached file keeps whatever byline was baked in on first render — pass `force_regenerate: true` to refresh it).
`force_regenerate`	No	If true, ignore the cached DOCX/PDF and re-render. No effect on md (markdown is canonical).

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes
`_meta`	Yes	Provenance envelope — data lineage for every MCP response
`format`	Yes
`filename`	Yes
`expires_at`	Yes
`from_cache`	Yes
`size_bytes`	Yes
`content_type`	Yes
`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."

Changed5 schema fields changedAug 5, 2026

changedInput schema / properties / author_name / description

Previous value: -"Display name of the report's author, shown as a named byline ('By {name}') on the docx masthead — the way a real research note credits an analyst. Omit to show just the date. Only affects `format=docx`; ignored on a cache hit (the cached file keeps whatever byline was baked in on first render — pass `force_regenerate: true` to refresh it)."New value: +"Display name of the report's author, shown as a named byline ('By {name}') on the masthead — the way a real research note credits an analyst. Omit to show 'Valuein Research'. Only affects the binary formats; ignored on a cache hit (the cached file keeps whatever byline was baked in on first render — pass `force_regenerate: true` to refresh it)."

changedInput schema / properties / force_regenerate / description

Previous value: -"If true, ignore the cached DOCX and re-render. No effect on md (markdown is canonical)."New value: +"If true, ignore the cached DOCX/PDF and re-render. No effect on md (markdown is canonical)."

changedInput schema / properties / format / description

Previous value: -"md = raw markdown (the same body the editor renders). docx = branded Word document — cover page crediting the named analyst, masthead repeated on page 2, running footer."New value: +"md = raw markdown (the same body the editor renders). docx = branded Word document; pdf = the same branded research-note design as a shareable PDF (Geist faces embedded, clickable citation links)."

changedInput schema / properties / format / enum

Previous value: -[
-  "md",
-  "docx"
-]New value: +[
+  "md",
+  "docx",
+  "pdf"
+]

changedOutput schema / properties / format / enum

Previous value: -[
-  "md",
-  "docx"
-]New value: +[
+  "md",
+  "docx",
+  "pdf"
+]

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"
+}

Changed1 schema field changedJul 8, 2026

changedInput schema / properties / format / description

Previous value: -"md = raw markdown (the same body the editor renders). docx = branded Word document — a compact masthead on page 1, no dedicated cover page, running footer."New value: +"md = raw markdown (the same body the editor renders). docx = branded Word document — cover page crediting the named analyst, masthead repeated on page 2, running footer."

Changed4 schema fields changedJul 7, 2026

addedInput schema / properties / author_name

Added value: +{
+  "description": "Display name of the report's author, shown as a named byline ('By {name}') on the docx masthead — the way a real research note credits an analyst. Omit to show just the date. Only affects `format=docx`; ignored on a cache hit (the cached file keeps whatever byline was baked in on first render — pass `force_regenerate: true` to refresh it).",
+  "maxLength": 120,
+  "type": "string"
+}

changedInput schema / properties / format / description

Previous value: -"md = raw markdown (the same body the editor renders). docx = branded Word document with cover + back page."New value: +"md = raw markdown (the same body the editor renders). docx = branded Word document — a compact masthead on page 1, no dedicated cover page, running footer."

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"
```
AddedMay 19, 2026

TDQS

A4.6/5.0

Behavior5/5

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

It discloses substantial behavior beyond the annotations: 15-minute URL expiry, R2 caching after first build, force_regenerate cache busting, author_name's effect only on first render, and the tier gate mirroring get_report. These are exactly the side effects and conditions an agent needs, and nothing contradicts the 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?

The core action is front-loaded in the first sentence, and later paragraphs are logically grouped by formats, caching, and access. The description is somewhat longer than necessary, with typography-level branding details that an agent does not strictly need to invoke the tool, though they do set output expectations.

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 rendering/download tool, it covers output kind, URL lifetime, format semantics, cache behavior, regeneration triggers, byline handling, and access policy. Since an output schema exists, return-value details are not required, and no schema-controlled parameter is left unexplained.

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 100% and each parameter already has a solid description, so the baseline is 3. The description adds extra semantic value: format=md is instant/no compute, docx/pdf share one branded design, force_regenerate is recommended right after update_report, and author_name is frozen on cache hits.

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 precise verb and resource: it returns a 15-minute presigned download URL for a report. The format enum, caching notes, and tier-gate reference to get_report make the tool's role and output unmistakable, even among many siblings.

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 gives clear context for when to use the tool: after a report exists, and it explicitly explains format-specific behavior (md is instant from cache, docx/pdf render and cache) and when to pass force_regenerate, e.g. right after update_report. It does not explicitly name alternatives like generate_research_brief_docx or state 'don't use this when...', so it falls just short of a full when/when-not guide.

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.

Render Report Download URL

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources