Qué hace
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.
Parámetros
Esta herramienta no recibe argumentos.
Anotaciones
Las pistas que el servidor envía con esta herramienta. Un cliente las lee para decidir si te pregunta antes de llamarla.
- Solo lectura
readOnlyHint: true - No cambia nada.
- Destructiva
destructiveHint: false - Solo agrega o lee; no quita ni sobrescribe nada de lo que ya existe.
- Idempotente
idempotentHint: — - No aplica: la herramienta no cambia nada.
- Mundo abierto
openWorldHint: false - Solo toca tu propia cuenta de Done.
Qué tokens pueden llamarla
Una conexión hecha con OAuth tiene acceso completo. Un token de Ajustes → Acceso de agentes → Tokens de MCP adicionales se puede acotar, y un token acotado nunca ve más allá de su proyecto o espacio de trabajo.
- Acceso completoPermitido
- Token de solo lecturaPermitido
- Token de un proyectoPermitido
- Token de un espacio de trabajoPermitido
Pruébala
Con Done conectado, pídele a tu asistente algo como:
“¿Qué rutinas te programé?”
Conecta Done a tu asistente
Un endpoint MCP por cuenta, con OAuth o con un token. Configuración paso a paso para cada cliente: