What it does
Find open work that has gone quiet, with the evidence needed to decide what to do about it — the grooming sweep. Returns, per flagged task: days inactive (counting comments and status changes, not just field edits), age, subtask progress, how many blockers are still open, whether a decision is already waiting on the human, and reason codes explaining the flag (never_started, past_due, subtasks_complete, resurface_due, blocked, no_activity). Pass days to set the quiet threshold (default 30) and limit to cap the result (default 50). Tasks already parked on a human (pending approval, plan proposed, needs input) are excluded — they are queued, not stale. This tool only reports: propose a disposition with ask_decision, defer with update_task resurface_date, or split with decompose_task. Only a human can set wont_do.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
days | integer | Optional |
|
limit | integer | Optional |
|
Annotations
The hints the server sends with this tool. A host reads them to decide whether to ask you before a call.
- Read-only
readOnlyHint: true - Changes nothing.
- Destructive
destructiveHint: false - Only adds or reads; nothing already there is removed or overwritten.
- Idempotent
idempotentHint: — - Doesn't apply: the tool changes nothing.
- Open world
openWorldHint: false - Touches only your own Done account.
Which tokens can call it
A connection made with OAuth has full access. A token from Settings → Agent access → Extra MCP tokens can be narrowed, and a narrowed token never sees beyond its project or workspace.
- Full accessAllowed
- Read-only tokenAllowed
- Single-project tokenRefused
- Single-workspace tokenAllowed
Try it
With Done connected, ask your assistant something like:
“Which open tasks have gone quiet for more than two weeks?”
Connect Done to your assistant
One MCP endpoint per account, over OAuth or a token. Step-by-step setup for each client: