Skip to main content
Glama

snooze_task

Hide an open task from boards, the menu bar, and task lists until a set wake time, while keeping its status, due date, project, and recurrence unchanged.

Instructions

Snooze an open task: hide it from Lilt's board, menu bar and list_tasks until a wake time. Status, due date, project and recurrence are unchanged. Pass exactly one of preset or until.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "snooze_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoTask id — full UUID or a unique prefix (as shown in list_tasks, e.g. 'a1b2c3d4').
titleNoTask title — exact (case-insensitive) or a unique partial match. Use instead of id.
untilNoISO-8601 datetime (or YYYY-MM-DD for 9 AM that day).
presetNoend-of-day = 4 PM today (tomorrow if past 4 PM); N days/1 week = 9 AM that day.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the visibility surfaces affected and, unusually, enumerates what is preserved (status, due date, project, recurrence). It does not cover reversibility via unsnooze_task, what happens if the task is already snoozed or completed, or what the call returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the purpose, then invariants, then the parameter constraint. No redundant restatement of the title or schema text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers effect, non-effects and the preset/until exclusivity for a 4-parameter mutation with no annotations. With no output schema present, the absence of any statement about what the call returns leaves a small gap, as does the unaddressed already-snoozed case.

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

Parameters3/5

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

Schema coverage is 100%, including enum values and a mutual-exclusion-relevant pair, so the baseline is 3 per the calibrated rule. The description does add one genuine constraint absent from the schema (required is empty, no oneOf), namely that exactly one of `preset` or `until` must be supplied, but adds nothing else about the id/title selectors.

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 verb and resource ('Snooze an open task') plus the concrete effect: hidden from Lilt's board, menu bar and list_tasks. An agent can distinguish this from unsnooze_task and update_task from the description alone, since the non-effects (status, due date, project, recurrence unchanged) are spelled out.

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?

The scope 'open task' establishes when this is applicable and the wake-time framing distinguishes it from a plain update. It does not explicitly name unsnooze_task as the reversal path or say what to do with closed tasks, so there is clear context but no explicit alternates.

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