state
Test Signal (synthetic fire)
test_signalBenchmark and above
Fire a synthetic notification through EVERY channel the signal is configured with. Use this immediately after `create_signal` to verify the channels (email address valid / webhook URL reachable + HMAC verification on the receiver). The synthetic fire is logged with a `[TEST]` ...
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( "test_signal", arguments={ "signal_id": "EXAMPLE"})print(result)Direct tool call:test_signal(...)
Inputs
| Parameter | Type | Required | Description |
|---|---|---|---|
signal_id | string | required | Identifier of the signal to fire a synthetic test notification through, as returned by create_signal or list_signals. |
Output Fields
signal_idoutcomechannel_typestatus_codeerror_messagechannel_resultsExample Response
Illustrative
response.jsonjson
{ "signal_id": null, "outcome": null, "channel_type": null, "status_code": null, "error_message": null, "channel_results": 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.