> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/stackai-mcp/starter-prompts/find-an-answer-in-company-knowledge.md).

# Find an answer in company knowledge

Answer a question from material in an accessible knowledge base.

## Prompt

> Find the knowledge base \[name] and retrieve evidence for: \[question]. Expand the most relevant chunks and answer using only supported evidence. Include document names and source locators where available, and say what is missing or truncated. Do not run a project.

Uses `kb_list`, `kb_search`. The assistant synthesizes the answer from returned chunks.

## Check the result

An evidence-based answer with source names and gaps called out. If the assistant cannot complete the task, ask for the missing access, connection, or input rather than accepting a guessed result.

## Tool reference

* [kb\_list](https://docs.stackai.com/stackai-mcp/tool-reference/connections-knowledge-and-discovery/kb-list.md)
* [kb\_search](https://docs.stackai.com/stackai-mcp/tool-reference/connections-knowledge-and-discovery/kb-search.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/stackai-mcp/starter-prompts/find-an-answer-in-company-knowledge.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
