well_snooze_schedule
shallowio.github.WellApp-ai/well-mcp · Verify this server
Snooze one workspace routine: skip its runs until a moment the person names, then let it carry on by itself with the same rhythm. Use it when the person asks to skip a few days, take a break from a routine, or snooze it: "snooze my morning brief until Monday", "skip my brief this week", "no brief before the 20th". The routine stays armed and the person does not have to resume it. REQUIRED: schedule_id (from well_list_schedules) and snooze_until, an ISO 8601 date and time with an offset, in the person's time zone. A day with no time means the start of that day, so "until Monday" lets Monday's run happen. The routine runs again at its first scheduled time at or after snooze_until. When the person gives a span and no date, do not ask for one: "a few days" is 3 days, "a week" is 7 days. Pick the date, snooze, and say it so the person can correct it. Works on an active routine that runs on a clock. A routine that starts on an event has no clock to delay: the call is refused, so tell the user and offer to cancel it instead. Do NOT use this to stop a routine: "disable my morning brief", "stop my brief" and "turn it off" use well_cancel_schedule. Do NOT use it to change the rhythm, the time or the job (use well_update_schedule), or to pause a routine until the user resumes it (use well_update_schedule with status "paused"). Snoozing draws no confirmation card. Say the date of the next run the result returns, in plain words. When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass `workspace_id` on the call.
1 trials · measured 2 days ago
well_snooze_schedule scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against io.github.WellApp-ai/well-mcp, measured 18 Oct 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- gated
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-10-18 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/005baad3-808a-42ed-88a8-0f53176b333d)