---
url: /build/employee-tools.md
description: >-
  What an employee's own AI chat can do when it is connected to DutyGraph, and
  the interview rules it follows.
---

# Employee tools

Built

When an employee connects their own AI chat, DutyGraph interviews them about their work and turns the answers into Task Cards. They only ever see their own records and the company files they are allowed to read.

## What a person says

| They say | What happens |
| --- | --- |
| "Start" or "Help" | `start` shows a welcome and what they can do |
| "Find my work" or "Interview me" | `find_my_work` works out where they begin, from their role. A CEO starts with vision and strategy. A department head starts with the department. Everyone else starts with Task Cards. |
| "Find my tasks" | The same tool, focused on their own recurring work |
| "Resume" or "Continue" | `get_interview_session` shows what is answered and the next step |
| "Show my alignment" | `get_my_alignment` shows the chain from the company's vision down to their Task Cards |
| "I have an idea" | `open_suggestion_box` takes a process improvement and asks why until it reaches the cause |
| Anything else they want to send | `send_to_dutygraph` takes any text. Nothing is turned away. |

## The role comes with them

The tools return the person's approved [role profile and its AI persona](../operate/role-ai.md). The assistant reads it before it helps with a task. When a task is outside the person's decision rights, the assistant says who decides. When no profile is approved, it asks the person and never invents a role.

## The interview rules

DutyGraph keeps the interview, not the chat. That is why a person can stop and come back.

* **One to three questions at a time.**
* **Every answer is saved when it is given.** The person is told, for example "Saved ✓ 7 of 24". Answers are never batched for the end.
* **"I don't know" and "Skip for now" are always offered.**
* **Checkpoints.** At the end of a step the person can continue or save and finish later.
* **A saved answer is never asked again.**
* **Nothing is guessed.** A field the person did not say or confirm stays empty.
* **A card is sent only when it is complete and the person says yes to the preview.** DutyGraph refuses cards that skip the interview.

Where the client supports it, DutyGraph shows its own interview card with buttons. Where it does not, the assistant asks the same questions in text.

## Task Card tools

| Tool | What it does |
| --- | --- |
| `start_work_discovery` | Starts or resumes a Task Card interview and returns the fields DutyGraph needs |
| `save_discovery_candidates` | Saves the tasks found, with the evidence for each |
| `record_task_interview` | Saves each answer |
| `evaluate_task_card_completeness` | Says whether a card is ready for review |
| `submit_task_card_drafts` | Sends the card after the person says yes |
| `list_my_task_cards`, `list_my_drafts`, `list_my_gaps` | What they have, what is in progress and what is missing |

The full list with every description is in [MCP tools](../reference/mcp-tools.md).
