Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Stage Action

stage_action

Propose an MCP tool call for human approval BEFORE running it. Call this — instead of calling the tool directly — whenever an autonomous or unattended caller (a scheduled standing agent, an unattended agent-runner run, or any MCP client operating without a human watching) is about to perform a write it knows or suspects is risky. The target tool's OWN registered risk hints (readOnlyHint/destructiveHint) decide the tier: GREEN (read-only) tools are never staged — this call is then a no-op passthrough (result: 'not_required') and the caller should just invoke the tool directly. AMBER (reversible write to the caller's own state) and RED (destructive or outward-facing) tools ARE staged: this call does NOT execute anything — it only records the proposal and returns a staged_action_id plus an undo handle (call undo_change to withdraw the proposal while it is still pending; null when nothing was staged). A human (or any client acting on the human's behalf) later calls approve_staged_action or reject_staged_action to decide it. Tier: sp500+ (sample rejected — guest has no saved state).

Input Schema

Name	Required	Description
`origin`	Yes	Free-form label identifying who/what is proposing this action — e.g. 'agent-runner:managed', 'claude-connector', 'cursor', or any caller-supplied identifier. Lets a human distinguish which session/agent proposed a given write.
`tool_args`	No	The exact arguments to replay through that tool if/when a human approves.
`tool_name`	Yes	The MCP tool this action would call once approved (e.g. 'save_thesis', 'create_signal', 'publish_report').

Output Schema

Name	Required	Description
`undo`	Yes	How to put the record back as it was before this write: call `undo_change` with these args. Null when nothing changed or the change could not be recorded.
`_meta`	Yes	Provenance envelope — data lineage for every MCP response
`result`	Yes
`risk_tier`	Yes
`staged_action`	Yes
`staged_action_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 1, 2026

addedOutput schema / properties / undo

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "args": {
+          "additionalProperties": false,
+          "properties": {
+            "change_id": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "change_id"
+          ],
+          "type": "object"
+        },
+        "tool": {
+          "const": "undo_change",
+          "type": "string"
+        }
+      },
+      "required": [
+        "tool",
+        "args"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "How to put the record back as it was before this write: call `undo_change` with these args. Null when nothing changed or the change could not be recorded."
+}

changedOutput schema / required

Previous value: -[
-  "_meta",
-  "result",
-  "risk_tier",
-  "staged_action_id",
-  "staged_action"
-]New value: +[
+  "_meta",
+  "result",
+  "risk_tier",
+  "staged_action_id",
+  "staged_action",
+  "undo"
+]

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

Changed1 schema field changedAug 7, 2026

changedInput schema / properties / tool_name / description

Previous value: -"The MCP tool this action would call once approved (e.g. 'save_thesis', 'create_alert', 'publish_report')."New value: +"The MCP tool this action would call once approved (e.g. 'save_thesis', 'create_signal', 'publish_report')."

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

AddedJul 3, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses that nothing executes, that the call only records a proposal, the tier derivation from the target tool's own readOnlyHint/destructiveHint, the no-op passthrough behavior for GREEN tools, and the contents of the response (staged_action_id, undo handle, null when nothing staged). Annotations only declare the generic write/non-destructive profile; the description supplies the actual decision logic.

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 rule (propose before running, don't call directly) is front-loaded, and most sentences carry operational content. It is dense to the point of being a single wall of text with heavy parentheticals, and the trailing 'Tier: sp500+ (sample rejected — guest has no saved state)' is bolted on rather than integrated.

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 three-parameter staging tool with an output schema, the description covers the decision to stage, the no-op case, the tier derivation, and what the caller receives and should do next. Nothing an agent needs in order to invoke it correctly 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%, so tool_name, origin and tool_args are already documented in the schema, and the description largely restates them indirectly. It adds the useful notion that tool_args are replayed verbatim on approval, but does not explain origin's role or the nested-object semantics any further. Baseline 3 is correct.

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 and resource: 'Propose an MCP tool call for human approval BEFORE running it', and immediately distinguishes itself from the default path ('Call this — instead of calling the tool directly'). An agent can tell this apart from approve_staged_action / reject_staged_action / undo_change 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 trigger conditions are given (autonomous or unattended callers about to perform a risky write) plus a clear exclusion rule (GREEN read-only tools are never staged; just call the tool directly). It also names the follow-up tools by name — approve_staged_action, reject_staged_action, undo_change — with the condition that selects each.

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.