> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dapta-mcp/skills/workspace-inventory.md).

# Workspace Inventory

Ask Claude what your workspace actually holds: phone numbers and who answers each one, knowledge bases and their sources, and the WhatsApp templates you can send.

Ask Claude what your workspace actually holds. This is the place to check before you build something that depends on a phone number, a knowledge base or a WhatsApp template.

{% hint style="info" %}
Everything on this page is **read-only**. Claude looks things up and reports back.
{% endhint %}

## Phone numbers

See the phone numbers in your workspace and which agent answers each one.

**Try saying:**

* "Which phone numbers does this workspace have?"
* "Which agent answers this number?"

**Behind the scenes:** `list_phone_numbers`.

***

## Knowledge bases

See your knowledge bases and check whether their sources really loaded.

**Try saying:**

* "List my knowledge bases."
* "Did all the sources in the product knowledge base load correctly?"

**Behind the scenes:** `list_brains`, `get_brain`.

***

## WhatsApp templates

See the WhatsApp templates in your workspace and which ones can actually be sent.

**Try saying:**

* "Which WhatsApp templates can I send right now?"
* "Is my appointment reminder template approved?"

**Behind the scenes:** `list_whatsapp_templates`.

***

## Related

{% content-ref url="/pages/orGP2lWwSOVddGYKWdXn" %}
[Accounts, Identity & Billing](/dapta-mcp/skills/accounts.md)
{% endcontent-ref %}


---

# 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.dapta.ai/dapta-mcp/skills/workspace-inventory.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.