state
Update Signal
update_signalBenchmark and above
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...
Example Call
example_call.pypython
# Using the Valuein MCP server from Python (via MCP SDK)# Or call directly from Claude / Cursor after setup result = await client.call_tool( "update_signal", arguments={ "alert_id": "EXAMPLE"})print(result)Direct tool call:update_signal(...)
Inputs
| Parameter | Type | Required | Description |
|---|---|---|---|
alert_id | string | required | The signal's `id` from `list_signals` / `create_signal`. |
name | string | optional | New human-readable label. |
condition | object | optional | New condition — the same discriminated union `create_signal` takes. Replaces the stored condition entirely. |
channels | array | optional | New delivery list (up to 4, each a distinct type+target). Replaces the stored list entirely; the first entry becomes `channel`. |
Output Fields
signalcron_indexedExample Response
Illustrative
response.jsonjson
{ "signal": null, "cron_indexed": null}Shape only — field names match the live schema; values are placeholders, not real filings. See MCP server for the structured response shape.
Notes
Available from the Benchmark plan and above.
Plan Access
Sample (guest)
Not includedBenchmark (token)
AvailablePro
AvailableInstitutional
AvailableRelated Tools
Index names are trademarks of their owners; Valuein is not affiliated with or endorsed by any index provider.