> 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/tools-reference.md).

# Tools Reference

Once Dapta is connected, you talk to Claude in plain language and it handles the rest. You never pick a command or name anything technical. You describe what you want, and Claude does it inside your connected workspace.

{% hint style="info" %}
You do not need to memorize anything on this page. Just ask for what you want in your own words. This page is here so you can see, at a glance, the kinds of things Claude can help with.
{% endhint %}

Everything Claude does happens in the one workspace tied to your API key. You never tell Claude which workspace to use, and it can only see and touch that workspace's data.

***

## What "ask Claude to..." looks like

You do not learn a syntax. You just talk. For example:

> "Create a voice agent for booking demos."
>
> "Show me last week's call statistics."
>
> "Improve my agent's opening line based on recent calls."

Claude figures out the steps and, whenever it is about to change something, it shows you a preview and waits for your go-ahead before applying it. Reading and reporting never need a preview.

***

## 1. Voice agents

Ask Claude to:

* Create a new voice agent from a short description of what it should do.
* Configure an existing agent: its purpose, instructions, and settings.
* Improve or calibrate an agent's prompt so it handles calls better.
* Review how an agent is performing on its calls.

## 2. Text and WhatsApp agents

Ask Claude to:

* Build a text agent and set up how it should respond.
* Connect a text agent to WhatsApp so it can chat with your customers there.
* Review a text agent's conversations and message activity.

## 3. FlowStudio automations

Ask Claude to:

* Design an automation flow that connects your agents and tools together.
* Validate a flow before you use it, so you know it is set up correctly.
* Review how your existing flows are running.

## 4. Call and lead analytics

Ask Claude to:

* Pull call statistics and connection rates for your agents.
* List and dig into recent calls.
* Surface lead intelligence, such as which calls look like qualified leads.
* Spot the best times of day and week to reach people.

## 5. Sales-meeting insights

Ask Claude to:

* Analyze your recorded sales meetings.
* Get clear summaries and suggested next steps from each meeting.

## 6. Identity and billing

Ask Claude to:

* Check your account and workspace details.
* Review your credit balance and usage.
* Look up your subscription details.

## 7. Research and docs

Ask Claude to:

* Research a company from its website and pull together what it finds.
* Search Dapta's documentation to answer how-to questions.

***

## How your data stays safe

Dapta's connection is built so Claude can be helpful without putting your workspace at risk.

* **Your workspace only.** Your API key is tied to a single workspace. Claude can never reach another workspace or account.
* **Preview, then confirm.** Whenever Claude is about to change something (an agent, a prompt, a flow, or a ticket), it shows you a preview first and waits for your confirmation before applying it. Reading information never needs a preview.
* **Key hygiene.** Your key is shown only once and cannot be recovered later. There is one active key per workspace. To rotate it, revoke the old one and create a new one.

{% hint style="info" %}
Not sure what to ask? Start simple, for example "Create a voice agent in Dapta," and Claude will guide you from there.
{% 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://docs.dapta.ai/dapta-mcp/tools-reference.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.