Qué hace
Stop the whole board: every agent on this account stops being handed work until a human resumes it. This is pause_task one tier up, and the difference is what it is FOR — pause_task takes one task off the queue and you carry on with the rest; this says the run itself should not continue. Use it when what you hit is not about one task: the account's credentials are gone, every task is failing the same way, you are looping across tasks rather than inside one, or you can see a run about to spend a lot for nothing. Prefer pause_task when the wall is one task's. After this, list_my_tasks and next_task both REFUSE and give back your reason instead of an empty queue — deliberately, so the run that finds the board stopped logs why it stopped rather than "nothing to do". Work you already hold is not stranded: you can still comment on, tick off and close out a task in progress. reason is required and is the whole value of the call. You cannot un-pause: resuming is a human action in the app, so an agent that stopped the board can't restart it. Pass workspace_id when you belong to more than one workspace — list_workspaces has the ids.
Parámetros
| Nombre | Tipo | Obligatorio | Descripción |
|---|---|---|---|
workspace_id | string | Opcional | Which board to stop. Optional when you only belong to one workspace; required otherwise, so a stop this wide is never aimed by guesswork. |
reason | string | Obligatorio | What you hit, and what you'd already tried. Shown on the workspace and handed back to every later queue call. |
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: false - Cambia datos de tu cuenta de Done.
- Destructiva
destructiveHint: false - Solo agrega o lee; no quita ni sobrescribe nada de lo que ya existe.
- Idempotente
idempotentHint: false - Cada llamada puede agregar algo nuevo, como un comentario, una ejecución o una tarea.
- 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 lecturaRechazado
- Token de un proyectoRechazado
- Token de un espacio de trabajoPermitido
Pruébala
Con Done conectado, pídele a tu asistente algo como:
“Todos los despliegues están fallando. Detén todo el tablero hasta que yo lo revise.”
Conecta Done a tu asistente
Un endpoint MCP por cuenta, con OAuth o con un token. Configuración paso a paso para cada cliente: