← All MCP tools

List routines

list_routines
Read-only

What it does

Read-only: the recurring routines a human has scheduled on your boards. Each routine spawns one ordinary task assigned to you per scheduled slot (daily / weekdays / monthly at a local time) and files a trigger for it, so its runs reach you through list_triggers and next_task like any other request — you work them with the usual gates and receipts. Each entry carries the schedule, its timezone, when it next runs, whether it is paused, its delegate (the roster agent whose lane its tasks land in; null means the default agent) and delegate_on_roster (false when that agent has since been removed from the roster, so its tasks actually land in the default lane; null with no delegate or no roster), the instructions its tasks inherit, and its recent runs (spawned, or skipped because the board was paused or the previous task was still open). There is deliberately no tool to create, change, pause or delete a routine: an agent that could schedule itself would be enqueuing its own work. If you think one should exist or change, say so with ask_decision.

Parameters

This tool takes no arguments.

Annotations

The hints the server sends with this tool. A host reads them to decide whether to ask you before a call.

Read-onlyreadOnlyHint: true
Changes nothing.
DestructivedestructiveHint: false
Only adds or reads; nothing already there is removed or overwritten.
IdempotentidempotentHint: —
Doesn't apply: the tool changes nothing.
Open worldopenWorldHint: 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 tokenAllowed
  • Single-workspace tokenAllowed

Try it

With Done connected, ask your assistant something like:

“Which routines have I scheduled for you?”

Connect Done to your assistant

One MCP endpoint per account, over OAuth or a token. Step-by-step setup for each client:

MCP setup overview →