> ## Documentation index
> Fetch the complete documentation index at: [llms.txt](../llms.txt)
> Use this file to discover all available pages before exploring further.

# Projects and runs tools

Nine tools to create projects, ask research questions, follow runs, approve plans, and read Sleuth’s answers.

Research runs are the only MCP calls that use credits. See [How a research run works](mcp-run-lifecycle.md) for the order to call these in.

### `create_project`

Create a new research project. Returns `project_id` and status `idle`.

| Input | Type | Notes |
| --- | --- | --- |
| `name` (required) | string | 1 to 255 characters |

### `send_message`

Send a research question, an answer to a clarification, or an action to a project. Send exactly one of `message` or `action`. Returns a 202 acknowledgement right away.

| Input | Type | Notes |
| --- | --- | --- |
| `project_id` (required) | string | Project UUID |
| `message` | string | The question or clarification answer |
| `action` | string | `cancel`, `approve_plan`, `approve_schema`, `reject_plan`, or `reject_schema` |
| `feedback` | string | Only with `reject_plan` or `reject_schema`. Tells Sleuth what to change. |

To attach files, call `upload_document` first. Credits: a research question uses one credit per analytical cell the run fills.

### `get_project`

Get the full project state, including its status. This is the main polling call. When the status is `awaiting_clarification`, read the latest message with `get_messages` and answer with `send_message`.

| Input | Type | Notes |
| --- | --- | --- |
| `project_id` (required) | string | Project UUID |

Respect the `retry_after` hint, in seconds, between polls.

### `wait_for_update`

Wait until the project’s status changes, or until the time budget runs out. Returns the latest state, plus `status_changed` and `waited_seconds`. Chain calls for long runs.

| Input | Type | Notes |
| --- | --- | --- |
| `project_id` (required) | string | Project UUID |
| `timeout_seconds` | number | Default 180, maximum 300 |

### `get_messages`

List the user and Sleuth messages in a project, including Sleuth’s written answers and questions.

| Input | Type | Notes |
| --- | --- | --- |
| `project_id` (required) | string | Project UUID |
| `limit` | integer | 1 to 200, default 50 |
| `offset` | integer | Default 0 |

### `list_projects`

List the projects the signed-in user or key can see.

| Input | Type | Notes |
| --- | --- | --- |
| `limit` | integer | 1 to 100, default 20 |
| `offset` | integer | Default 0 |

### `update_project`

Rename a project.

| Input | Type | Notes |
| --- | --- | --- |
| `project_id` (required) | string | Project UUID |
| `name` (required) | string | The new name |

### `delete_project`

Delete a project and everything in it. This can’t be undone, so confirm with the user first.

| Input | Type | Notes |
| --- | --- | --- |
| `project_id` (required) | string | Project UUID |

### `export_project`

Export a full snapshot of a project. It can be very large, and datasets are capped at 10,000 rows each. Prefer the dataset and chart tools when an agent only needs part of it.

| Input | Type | Notes |
| --- | --- | --- |
| `project_id` (required) | string | Project UUID |

## Related

- [How a research run works](mcp-run-lifecycle.md): Create a project, send the question, wait for the status to change, handle approvals and clarifications, then read the datasets and the answer.
- [Datasets and charts tools](tools-datasets.md): Seven tools to read the datasets and charts a run builds: page through rows, download CSV, compare versions, and get charts as specs or SVG.
- [Your documents tools](tools-documents.md): Five tools to add your own files to a project, search them, get download links, and remove them.

*Updated November 9, 2026.*
