omniseek_sensor
Create a standing query that runs on a schedule and alerts you only to new matches or missing tracked items.
Instructions
Use WHEN you want to MONITOR a query over time and be told only what's NEW: standing queries with novelty detection. ONE verb; action picks what to do.
Tool name: omniseek_sensor (your MCP config adds its own prefix; never guess one). Not in your tool list? ToolSearch "omniseek_sensor".
create (query; optional sources, schedule hourly | daily | weekly, notify, notify_if, notify_if_match "any" | "all", detect_absence, notify_source): register a sensor; returns it with its id (and schedule_note when the deployment needs a SERVICES.tsv row to run it). update (sensor_id, notify_source): change its push source ("" = default); returns {updated, sensor}. list: all sensors with last-run stats. delete (sensor_id): returns {deleted}. run (sensor_id): run it now; returns new_count and new_titles. notify=True pushes new results of scheduled runs (notify_if narrows that to keyword matches); detect_absence also alerts when a tracked stable-source item disappears. An unknown action or a missing required argument returns {error}. More: omniseek docs/TOOLS.md, omniseek_sensor.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"action": "<action>"
},
"name": "omniseek_sensor"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | ||
| action | Yes | ||
| notify | No | ||
| sources | No | ||
| schedule | No | daily | |
| notify_if | No | ||
| sensor_id | No | ||
| notify_source | No | ||
| detect_absence | No | ||
| notify_if_match | No | any |