Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Unpublish Claim (back to private)

unpublish_claim

DestructiveIdempotent

Revert a published claim (public or unlisted) back to private — removes it from the author's /[handle] profile and excludes it from the public claim-accuracy aggregate. The inverse of publish_claim. Owner-only, idempotent. Tier: sp500+ (sample rejected).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`claim_id`	Yes	Id returned by `save_claim` or `list_claims`.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`_meta`	Yes	Provenance envelope — data lineage for every MCP response
`claim`	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 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"
+}

Changed1 schema field changedJul 3, 2026

addedOutput schema / properties / claim / properties / outcome_components

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Phase C resolved-metric breakdown ({evaluated, basis} from gradeClaim). Null when not yet resolved or resolved without a breakdown (manual); absent entirely on claims resolved before Phase C shipped — both mean 'no components recorded'."
+}

Changed1 schema field changedJun 23, 2026

addedOutput schema / properties / claim / properties / evidence / properties / source_links

Added value: +{
+  "description": "On-read enrichment of source_urls with interactive SEC viewer links.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "document_url": {
+        "description": "Direct link to the rendered primary document, or null.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "inline_viewer_url": {
+        "description": "SEC Inline-XBRL viewer on the rendered filing, or null when not iXBRL.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "sec_url": {
+        "description": "EDGAR filing-index page — always resolves.",
+        "type": "string"
+      },
+      "url": {
+        "description": "The original stored source_url (verbatim).",
+        "type": "string"
+      }
+    },
+    "required": [
+      "url",
+      "sec_url",
+      "document_url",
+      "inline_viewer_url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

AddedJun 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already indicate destructive and idempotent behavior. The description goes beyond this by disclosing concrete consequences: removal from the author's profile and exclusion from the public claim-accuracy aggregate. It adds meaningful behavioral context without contradicting 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.

Conciseness5/5

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

Two crisp sentences deliver the action, target state, side effects, ownership requirement, idempotency, and access tier with no filler. Key behavioral information is front-loaded, and every clause 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?

For a single-parameter mutation with a full schema, output schema, and annotations, this description covers everything an agent needs: what changes, what is affected, who may call it, whether it is idempotent, and its relationship to the inverse operation. Nothing essential is missing.

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

Parameters3/5

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

Schema description coverage is 100%, and the claim_id parameter already explains where the ID comes from. The description does not add parameter-level detail, but the schema carries that burden fully, so the baseline 3 is appropriate.

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 specific verb ('Revert'), the exact resource ('a published claim'), and the target state ('back to private'). It also defines scope by mentioning both public and unlisted claims, and explicitly names its inverse relationship to publish_claim, making it easy to distinguish from delete_claim or unpublish_report.

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?

Clearly conveys when to use it: to undo a publication, with 'Owner-only' specifying authorization and 'idempotent' signaling safe retry. It identifies itself as the inverse of publish_claim, though it does not explicitly state when not to use it versus a sibling like delete_claim.

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.