Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Update Signal

update_signal

Idempotent

Edit an existing signal IN PLACE — rename it, change what it watches, or change where it delivers — keeping its id, its fire history (trigger_count, last_triggered_at) and every inbox item and delivery already tied to it. Pass only the fields to change; omitted fields keep their stored value. channels REPLACES the whole delivery list (1–4, distinct type+target); a webhook entry that keeps its URL and omits hmac_secret keeps the stored secret. A soft-deleted signal is refused — restore_deleted first. Same tier rules as create_signal: price_move / fundamental_change / watchlist_restatement conditions need Pro+. Cap-neutral: an edit never takes a signal slot. Returns undo (call undo_change to put name, condition and channels back as they were; refused if the signal changed since).

Input Schema

Name	Required	Description
`name`	No	New human-readable label.
`alert_id`	Yes	The signal's `id` from `list_signals` / `create_signal`.
`channels`	No	New delivery list (up to 4, each a distinct type+target). Replaces the stored list entirely; the first entry becomes `channel`.
`condition`	No	New condition — the same discriminated union `create_signal` takes. Replaces the stored condition entirely.

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
`signal`	Yes
`cron_indexed`	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",
-  "signal",
-  "cron_indexed"
-]New value: +[
+  "_meta",
+  "signal",
+  "cron_indexed",
+  "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."

AddedSep 17, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations declare idempotent/non-destructive, and the description adds substantial behavior beyond them: partial-update semantics (omitted fields retained), channels full-replacement with first entry becoming `channel`, webhook secret retention when hmac_secret omitted, soft-delete refusal, and the returned `undo` token with its staleness guard.

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?

Dense but front-loaded: the in-place/preserve-identity core leads, followed by ordered operational caveats (partial update, replacement, restore, tier, undo). No sentence is 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 partial-update mutation with an output schema present, the description covers everything an agent needs: which fields change, how replacement differs from patch, prerequisites, and the undo return path. Nothing material 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 coverage is 100%, so baseline is 3, but the description adds real meaning: pass-only-what-changes semantics and the hmac_secret retention rule that the schema does not state. The first-entry-becomes-channel detail partially overlaps the channels schema description, keeping this from a 5.

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 (edit) and resource (existing signal) with the key differentiating scope: IN PLACE, preserving id, fire history, and tied inbox items. This clearly distinguishes it from create_signal, delete_signal, and update_report without needing the 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?

Explicitly names prerequisites and alternatives: a soft-deleted signal must be restored via `restore_deleted` first, and `undo_change` reverses an edit. It also gives the tier rule (Pro+ for certain condition types) and clarifies cap-neutrality versus create.

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.