> For the complete documentation index, see [llms.txt](https://developers.epiqai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.epiqai.com/work-with-tools/available-epiq-ai-mcp-tools/documents.md).

# Documents

## `search_documents`

Searches the documents in a project and returns relevant document evidence. This is the workhorse: use it whenever you want to know what the case documents actually say. You can optionally restrict it to a single collection (use a collection from list\_collections).

#### Example prompts

* *"What do the documents say about the SEC subpoena timeline?"*
* *"Find anything about the September shipment delay."*
* *"Search the Acme production for mentions of 'material weakness'."*
* *"In this project, what do the emails say about the settlement offer?"*

{% hint style="info" %}
The connector returns relevant context plus source DOC\_ID links, then Claude reads that evidence to answer your question. It surfaces only the documents relevant to your question and quietly sets aside the rest, so the answer stays focused.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developers.epiqai.com/work-with-tools/available-epiq-ai-mcp-tools/documents.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.