What it does
Take responsibility for one request from list_triggers, so a fleet doesn't double-work an ask. Atomic: exactly one agent wins, and a second caller is told who holds it. This claims the REQUEST, not the task — follow it with claim_task (or next_task, which now ranks requested tasks first) to actually take the work, and comment_on_task to answer the person who asked. A withdrawn request can't be claimed.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
id | string | Required | The trigger id from list_triggers. |
agent | string | Optional | Your agent/model id, recorded as who picked the request up. |
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: false - Changes data in your Done account.
- Destructive
destructiveHint: false - Only adds or reads; nothing already there is removed or overwritten.
- Idempotent
idempotentHint: false - Each call can add something new, such as a comment, a run or a task.
- 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 tokenRefused
- Single-project tokenAllowed
- Single-workspace tokenAllowed
Try it
With Done connected, ask your assistant something like:
“Claim the request I just sent with Run now, then work on it.”
Connect Done to your assistant
One MCP endpoint per account, over OAuth or a token. Step-by-step setup for each client: