Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Publish Report (free)

publish_report

Idempotent

Publish a report for FREE at listed or unlisted visibility to build your public author profile. listed makes it discoverable via search_reports (keyword catalog search); unlisted keeps it out of the catalog but accessible by direct id (shareable link). Author can set a tier_required no higher than their own plan. All listings are free today (omit price_cents or set it to 0); paid listings are a future capability. ⚠️ VERIFIED BEFORE IT GOES OUT: every figure is checked against the filing it cites, and the publish is REFUSED (FIGURES_UNVERIFIED) if any number the filing contradicts has not been reviewed by a human. Call verify_report_figures FIRST and fix each differs — quote the filing's own display string with update_report, or record a disposition with save_figure_review. Figures that merely could not be checked do NOT block publishing. If verification itself is unreachable the publish is refused as VERIFICATION_UNAVAILABLE (retryable) rather than going out unchecked.

Input Schema

Name	Required	Description	Default
`report_id`	Yes
`visibility`	No		listed
`price_cents`	No	Currently must be omitted or 0 — all listings are free. A non-zero value is rejected until paid listings ship.
`tier_required`	No	Minimum subscriber tier to read the full body. Defaults to the author's plan.

Output Schema

Name	Required	Description	Default
`_meta`	Yes	Provenance envelope — data lineage for every MCP response
`report`	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 21, 2026

removedOutput schema / properties / vectorize_indexed
```
Removed value: -{
-  "type": "boolean"
-}
```

changedOutput schema / required

Previous value: -[
-  "_meta",
-  "report",
-  "vectorize_indexed"
-]New value: +[
+  "_meta",
+  "report"
+]

AddedJun 21, 2026
RemovedMay 12, 2026
AddedMay 12, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations declare non-read-only, non-destructive, idempotent, but the description adds genuinely new behavior: two named refusal states (`FIGURES_UNVERIFIED`, `VERIFICATION_UNAVAILABLE`), which is retryable, the rule that only human-reviewed contradicting figures block, and the tier_required ceiling against the author's own plan. Nothing here is a restatement of an annotation.

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 purpose, then ordered constraints, then the blocking warning — good structure. It is somewhat overlong: the 'free today / paid listings are a future capability' point is made twice (once in prose, once in the schema) and the all-caps warning styling is heavy, but no sentence is truly wasted.

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 gated mutation tool with an output schema present, the description covers the failure modes, the prerequisite chain, and every non-trivial parameter constraint. Return values can be omitted because an output schema exists, and the agent has everything needed to invoke correctly on the first try.

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

Parameters5/5

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

Schema coverage is only 50%, and the description compensates well: it defines the observable consequence of each visibility value, the constraint that `tier_required` cannot exceed the author's plan, and that `price_cents` must be omitted or 0 with non-zero rejected. Only `report_id` is left to the schema, which is acceptable for a self-evident id.

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?

Specific verb+resource ('Publish a report') with the two visibility modes defined in-line, and it names the sibling that consumes the result (`search_reports`). An agent can distinguish this from `publish_claim`/`publish_thesis` and from `render_report` without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit prerequisite ordering: call `verify_report_figures` FIRST, resolve each `differs` via `update_report` or `save_figure_review`, and the distinction that unverifiable figures do not block. It also states when to pick `listed` vs `unlisted`. This is the strongest part of the definition.

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.