Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Get Auditable Research File

get_research_file

Read-onlyIdempotent

Fetch the Auditable Research File behind one of the caller's own agent runs — the complete evidence chain an examiner asks for: the originating prompt, every tool the agent called in order, every fact_id it cited, every human approval, and which models were used. Assembled from the immutable audit ledger written as the run executed; nothing here is reconstructed or inferred. Name the subject EITHER way, and pass exactly one: report_id (a report you wrote or found — from create_report, list_my_reports or search_reports) or run_id (from list_agent_runs). Naming a REPORT is the richer call: it resolves the run behind that report AND adds two sections a run's ledger cannot carry — human_review (each figure a HUMAN verified, corrected, rejected or sourced externally, with who and when) and sources (the SEC filing, form, period and filed date behind each cited fact_id). It also echoes the resolved run_id. A run-keyed call omits both, because a run may produce several reports and 'the report for this run' has no honest answer; empty or absent there means NOT RESOLVED, never 'no sources'. format: "pdf" returns the SAME assembled file as a branded compliance PDF instead of inline JSON — a 15-minute presigned download URL (url + filename) for the human-facing artifact (cover with the completeness verdict, evidence chain table, provenance with clickable sec.gov links). The PDF is rendered fresh on every call — never cached — because an in-flight run's ledger can gain entries, and a stale 'complete' verdict is exactly the lie this document exists to prevent. ⚠️ ALWAYS READ completeness FIRST AND REPORT IT. completeness.complete is computed from the ledger, and completeness.gaps names every hole found — an irreversible action taken with no named approver, a state-changing action that cited no fact_id, an unrecorded model, a failed step. If you present this run as evidence, present the gaps too; a chain with holes that is quoted as if whole is the one thing this artifact exists to prevent. ⚠️ found: false IS NOT A FINDING ABOUT THE WORK. It is returned (not as an error) for an unknown id, an id belonging to another customer, and a report with no run on record — deliberately indistinguishable, so no caller can probe which. It means we hold no audit trail under that id. It does NOT mean the report is unaudited, unverified, or that the id does not exist, and it must never be reported that way. Tier: sp500+ (sample rejected).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`format`	No	json (default) = the assembled file inline. pdf = a presigned download URL for the branded compliance PDF — the human-facing artifact; rendered fresh on every call, never cached.	json
`run_id`	No	Run identifier, as returned by list_agent_runs. Pass this OR report_id, not both.
`report_id`	No	Report identifier — from create_report, list_my_reports or search_reports. Resolves the run behind that report and adds the human_review + sources sections. Pass this OR run_id, not both.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	No
`file`	No
`_meta`	Yes	Provenance envelope — data lineage for every MCP response
`found`	Yes
`run_id`	No
`filename`	No
`expires_at`	No
`size_bytes`	No
`content_type`	No
`expires_in_seconds`	No

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

Changed7 schema fields changedAug 5, 2026

addedInput schema / properties / format

Added value: +{
+  "default": "json",
+  "description": "json (default) = the assembled file inline. pdf = a presigned download URL for the branded compliance PDF — the human-facing artifact; rendered fresh on every call, never cached.",
+  "enum": [
+    "json",
+    "pdf"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / content_type
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / expires_at
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / expires_in_seconds
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / filename
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / size_bytes
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / url
```
Added value: +{
+  "type": "string"
+}
```

AddedAug 2, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond the readOnlyHint/idempotentHint annotations, the description discloses substantial behavioral detail: the file is assembled from the immutable audit ledger and 'nothing here is reconstructed or inferred'; the PDF is rendered fresh and never cached; completeness.complete is ledger-computed and gaps must be reported; and found:false is deliberately indistinguishable across unknown ids, other customers' ids, and reports with no run on record. This is exactly the contextual disclosure an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well front-loaded and each block covers a real decision or warning, but it is long and somewhat repetitive — the 'artifact exists to prevent' point is made twice, and several sub-clauses could be tightened. It is appropriately sized for the tool's complexity but not every sentence earns its place.

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 output schema, annotations, and the tool's complexity, the description is complete. It covers the two valid invocation paths, the richer report-keyed output, PDF rendering semantics, the mandatory completeness reading, the gaps reporting obligation, the ambiguous found:false case, and the access tier. Nothing material an agent needs to call this safely is missing.

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 meaning beyond the schema: the 'name EITHER way, pass exactly one' rule, why report-keyed calls are richer, the NOT RESOLVED semantics for absent sections in run-keyed calls, and the PDF presigned-download behavior. These are meaningful semantic additions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Fetch') and a specific resource ('Auditable Research File behind one of the caller's own agent runs'), then enumerates the evidence chain contents: prompt, tool calls, fact_ids, approvals, and models. It is unmistakably clear, but it does not explicitly differentiate this tool from closely related siblings like get_agent_run or forensic_audit, so it stops short of the top tier.

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 explicit selection logic: pass exactly one of report_id or run_id, explains why 'Naming a REPORT is the richer call,' and clarifies what a run-keyed call omits. It also warns that found:false must not be reported as a finding about the work. It does not, however, name alternative sibling tools or say when to use them instead of this one.

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.