Create watcher
refix_create_watcherCall refix_list_watchers first and do not create a duplicate. Create a Refix watcher. A watcher carries a goal: Refix keeps working on it against the workspace's connected data and reports what it finds to the chosen place. Use it for ongoing goals, not one-off questions. Tell the user that watchers count toward the workspace's Refix usage and that everyone in the workspace can see them. alerts: 'mcp_assistant' keeps alerts in Refix for you to read with refix_list_findings (no Slack post, no email); 'slack' or 'email' must match alert_channel from refix_get_context.
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": {
"objective": "<objective>",
"timezone": "<timezone>",
"alerts": "<alerts>",
"idempotency_key": "<idempotency_key>"
},
"name": "refix_create_watcher"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| alerts | Yes | ||
| timezone | Yes | The user's IANA timezone, such as 'Asia/Kolkata'. Ask the user if you do not know it. | |
| objective | Yes | The goal in the user's words. Examples: 'Find out why weekly orders fell and what would fix it.' 'Tell me when weekly signups drop more than 10%.' | |
| idempotency_key | Yes | A new random value, such as a UUID, for each new request. Reuse it only to retry the exact same request. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | ||
| alerts | Yes | ||
| status | Yes | ||
| objective | Yes | ||
| watcher_id | Yes | ||
| watcher_url | Yes | ||
| created_by_me | Yes | ||
| last_check_at | Yes | ||
| next_check_at | Yes |