Skip to main content
Glama

snooze_thread_triage

Destructive

Delay stale-thread triage prompts for 1–30 days (default 7) while keeping the thread open, so you can revisit unresolved work later without auto-dismissing it.

Instructions

Snooze stale-thread triage prompts for a few days (default 7).

    Soft only — thread stays open. Never auto-dismisses. Use
    confirm_thread_relevant when the outcome is still wanted now.
    

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": {
      "thread_id": "<thread_id>"
    },
    "name": "snooze_thread_triage"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDays to suppress stale-thread triage prompts (1–30); defaults to 7, measured from this call.
thread_idYesExact open or blocked thread ID whose stale-work prompts should be delayed; status is retained.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.22.0
    • addedInput schema / properties / days / description
      Added value: +"Days to suppress stale-thread triage prompts (1–30); defaults to 7, measured from this call."
    • addedInput schema / properties / thread_id / description
      Added value: +"Exact open or blocked thread ID whose stale-work prompts should be delayed; status is retained."
  2. Addedv0.17.0

TDQS

A3.6/5.0
Behavior3/5

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

The description adds real context beyond the annotations: the action is 'soft only', the thread 'stays open', and it 'never auto-dismisses', which reassures an agent that no data is lost. It does not explain what a repeated call does (the non-idempotent annotation suggests snoozes may stack or extend), nor the interaction with pending reminders — and 'soft/never dismisses' sits in mild tension with destructiveHint=true, so the agent gets mixed signals on safety.

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?

Three short sentences, front-loaded with the action and its default, then the safety caveat, then the alternative. Slight redundancy between 'Soft only' and 'Never auto-dismisses', but nothing is wasteful and it is easy to scan.

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?

With an output schema present and fully documented parameters, the description covers the essentials: what it does, how long, and what it does not do. The main omission is repeat-call behavior for a non-idempotent mutation, which an agent would want to know before snoozing twice.

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%, and both parameters carry detailed descriptions (1–30 range, default 7 measured from this call, exact thread ID with status retained). The description contributes only the parenthetical default of 7, which the schema already documents, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource — 'Snooze stale-thread triage prompts' — plus the default duration (7 days), which is enough for an agent to distinguish this from general thread mutation tools. It does not spell out the scope in terms of what a 'stale-thread triage prompt' is, but the resource is named precisely enough to act on.

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?

It gives an explicit routing rule: use confirm_thread_relevant 'when the outcome is still wanted now', which implies snoozing is for cases where the thread should be revisited later rather than confirmed. That is a clear alternative-plus-condition, though it does not enumerate when NOT to use this tool (e.g. already-done or dismissed threads).

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