Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Restore a Deleted Item

restore_deleted

Idempotent

Undo a soft-delete: restores a thesis, watchlist, signal, claim or report that delete_* archived. The record returns to the state it held before the delete — a closed thesis comes back closed, a paused signal comes back paused. When the item was deleted before the server began recording its prior state, prior_status_known is false and the response says which default was used. A restored report returns to its prior status AND visibility, so a report that was public comes back public and one that was private stays private; when that state predates the change that began recording it, the report returns private and prior_status_known is false rather than guessing at publication. Citation overrides are NOT restorable (that delete removes the row outright) — use the approval flow. Idempotent: restoring a live item succeeds and changes nothing. Tier: paid + free (sample rejected).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	The record's id. For a watchlist this is the `watchlist_id` returned by `delete_watchlist` — NOT its name, because deleting a watchlist frees its name for reuse.
`kind`	Yes	Which record type to restore. Citation overrides are not restorable.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`kind`	Yes
`_meta`	Yes	Provenance envelope — data lineage for every MCP response
`status`	Yes
`prior_status_known`	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 changedAug 7, 2026

changedInput schema / properties / kind / enum

Previous value: -[
-  "thesis",
-  "watchlist",
-  "alert",
-  "claim",
-  "report"
-]New value: +[
+  "thesis",
+  "watchlist",
+  "signal",
+  "claim",
+  "report"
+]

changedOutput schema / properties / kind / enum

Previous value: -[
-  "thesis",
-  "watchlist",
-  "alert",
-  "claim",
-  "report"
-]New value: +[
+  "thesis",
+  "watchlist",
+  "signal",
+  "claim",
+  "report"
+]

Changed3 schema fields changedJul 28, 2026

changedInput schema / properties / kind / description

Previous value: -"Which record type to restore. Reports and citation overrides are not restorable."New value: +"Which record type to restore. Citation overrides are not restorable."

changedInput schema / properties / kind / enum

Previous value: -[
-  "thesis",
-  "watchlist",
-  "alert",
-  "claim"
-]New value: +[
+  "thesis",
+  "watchlist",
+  "alert",
+  "claim",
+  "report"
+]

changedOutput schema / properties / kind / enum

Previous value: -[
-  "thesis",
-  "watchlist",
-  "alert",
-  "claim"
-]New value: +[
+  "thesis",
+  "watchlist",
+  "alert",
+  "claim",
+  "report"
+]

AddedJul 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the idempotentHint annotation, the description discloses that prior state is restored, explains the prior_status_known flag and its default fallback, details report-specific visibility restoration, confirms non-restorability of citation overrides, and notes tier restrictions. This is rich, annotation-complementing transparency with no contradiction.

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 dense but not bloated; every sentence carries edge-case or behavioral information an agent needs. The core purpose is front-loaded, and the trailing sentences address exceptions and idempotency rather than filler.

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 two-parameter tool with a full input schema, output schema, and annotations, the description covers behavior, edge cases, non-restorable types, idempotency, and tier gating. There is no obvious missing information an agent would need to call this tool correctly.

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%, so baseline is 3; the description adds value by explaining kind-specific restore behavior (e.g., a restored report returns to prior status AND visibility, with a private fallback) and reiterates the parameter semantics around non-restorable kinds. This goes beyond what the schema alone provides.

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 'Undo a soft-delete' and names the exact resources (thesis, watchlist, signal, claim, report) and the sibling delete_* tools it reverses. It also explicitly distinguishes non-restorable citation overrides and routes to the approval flow, so an agent can immediately tell this tool apart from deletes and approvals.

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?

Clear when-to-use context is established: restoring items archived by delete_* operations. The description gives an explicit exclusion and alternative for citation overrides (use the approval flow), but doesn't enumerate every non-usage scenario, which is acceptable given the tool's narrow scope.

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.