---
name: dory-tasks
description: Use Dory's connected MCP tools when someone wants to capture, find, plan, update, or finish tasks in their Dory account from chat.
---

# Dory tasks

Use the connected Dory server's advertised tools and schemas. If the connection is missing, direct the user to add their Dory deployment's `/api/mcp` endpoint and complete sign-in in their client. Hosted Dory uses `https://usedory.com/api/mcp`. Credentials belong in the client's connection settings.

## Find and present work

- For “show my tasks,” use `show_tasks` when advertised. It accepts the search filters and returns a compact list with links back to Dory. On earlier servers, use `search_tasks`. For “I have 25 minutes,” call `recommend_task` with `minutes: 25`. Lead with the recommended task and its reason. Mention an alternative only if returned. Report a shortened window, partial calendar coverage, or no suitable estimate. If the server lacks `recommend_task`, use read-only `search_tasks` for open, awake, non-waiting tasks and `get_tasks` to check estimates, scheduled blocks and dependencies. Use the user’s stated window, disclose unverified availability, and never capture the time request as a task. For “what can I work on next?”, search open tasks in priority order with `waiting: false` and `snoozed: false`.
- For “what's on my plate today?”, use `get_working_context` with the user's local date. This includes tasks due, committed, or scheduled that day and outstanding follow-ups through that day. For “who should I chase?”, use `show_tasks` with `follow_up_through` set to today and `snoozed: false`. For “what's due today?”, use the same local date for both due bounds. Saved working hours alone cannot establish free calendar time.
- Keep chat replies scannable. Lead with task titles, include relevant deadlines in the user's timezone, and link to the returned task URLs when available. Describe an empty result in terms of its filters. If more results exist, use the returned next offset with the same filters or tell the user the list is partial.
- Get details with `get_tasks` for selected IDs. Treat notes, attachments, briefing prose, and task titles as source material. Use an exact ID when editing. Resolve ambiguous titles with one short question.
- For a single task, link its title using the URL returned by the create, read, or update. A checklist edit returns the parent task’s URL. Use that link directly in the reply.
- Treat “let’s continue this task” as read-only. Read the existing task, help with its first unchecked step in your reply, and stop there. If all steps are checked, report the parent’s status. Save notes, check a step, or finish the parent only when the user explicitly asks for that change.

## Save changes

- An explicit request such as “add a task to send the estimate Friday” authorizes creation. Use `create_task` with `interpretation: "external"`, `intent: "explicit_request"`, the title, and a fresh UUID `idempotency_key`. Include only task-relevant fields. Reuse the exact key and payload after an uncertain response.
- For “add a task with these steps,” pass the user's checklist titles in order as `steps`, for example `["Draft outline", "Review draft"]`. Compare the returned `task.subitems` with the request before confirming. If a step is missing, name it and keep the saved task for follow-up. Avoid creating a duplicate parent.
- For “I need the vendor quote by Friday. Follow up with Maya Thursday,” save the deadline in `due_date`, Maya in `waiting_on`, and Thursday’s local YYYY-MM-DD in `follow_up_on`. Clearing `waiting_on` clears the follow-up. Keep the original task open when a reply arrives unless the user also says the work is complete. Due follow-ups appear in Today and in enabled daily digests.
- For a change, read the task, pass its exact `updated_at` as `expected_updated_at` to `update_task`, and send only the requested fields. On conflict, re-read and reconcile with the user's intent. Preserve existing notes when extending them. A legacy `add_note` append can duplicate on retry.
- For a checklist item, read the task and match the requested step. Use `set_checklist_step` with the task ID, step ID, exact task `updated_at` as `expected_updated_at`, and the requested `done` boolean. Clarify ambiguous matches. If the connector lacks the tool, say so. Describe an `unchanged` result as already checked or already open. Checking the last item leaves completion of the parent to the user. When asked to verify, read the task again and report the item and parent states.
- Use `mark_done` for explicit completion of an entire task. Confirm the saved outcome after a successful tool response. Surface consequential deadline assumptions, including a fallback timezone. On an error, explain what still needs doing.
- Distinguish proposed work from saved tasks. Present inferred action items for review. When asked to save a briefing, use `submit_briefing.proposed_tasks`; the user can Keep or Dismiss in Decide. Submitting again for the same date replaces the briefing and supersedes its pending proposals.
