Skip to main content
Glama

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

NameRequiredDescriptionDefault
queryNo
actionYes
notifyNo
sourcesNo
scheduleNodaily
notify_ifNo
sensor_idNo
notify_sourceNo
detect_absenceNo
notify_if_matchNoany

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / notify_source
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Notify Source"
      +}
  2. First observedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

With only readOnlyHint=false as annotation coverage, the description carries real weight and does: it discloses that scheduled runs push notifications, that notify_if narrows to keyword matches, that detect_absence fires on disappearance of a stable-source item, that an unknown action or missing required arg returns {error}, and that create may return schedule_note when a SERVICES.tsv row is needed. Gaps remain on delete irreversibility and any permission/auth requirements.

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?

Front-loaded WHEN clause followed by a compact per-action list with return shapes is an efficient structure. Some space is spent on self-referential meta text (config prefix warning, "Not in your tool list? ToolSearch...", docs pointer) that aids discovery but dilutes selection signal.

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?

Ten parameters, five actions, no output schema -- and the description supplies the return shape for each action ({updated, sensor}, {deleted}, new_count/new_titles, last-run stats). An agent has everything needed to pick an action and construct the call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and has no enums, yet the description gives meaning to all ten parameters, including the allowed schedule values (hourly | daily | weekly), the notify_if_match values ("any" | "all"), the empty-string convention for notify_source, and which params belong to which action. This is exactly the compensation the low coverage requires.

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 capability: standing queries with novelty detection, i.e. monitor a query over time and be told only what's new. The opening WHEN clause frames it as a monitoring tool, which separates it from the one-shot search/gather siblings without needing to name them. The five actions are enumerated so the agent knows the full surface.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit entry condition ("Use WHEN you want to MONITOR a query over time and be told only what's NEW") plus a short gloss per action (create registers, run executes now, delete removes). It does not name an alternative tool or state when NOT to use this, so routing to omniseek_search for a single ad-hoc lookup is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.