---
name: agentwaves
description: Work with an AgentWaves workspace from an AI app: the Chief of Staff and its team of Agents, their calls, contacts, tasks and campaigns. Use when the user asks about their calls, callers, leads, follow-up tasks, campaigns or Agents, or wants an Agent to call someone. Requires the AgentWaves MCP server (https://agentwaves.net/mcp).
---

# AgentWaves

AgentWaves gives a business owner a Chief of Staff Agent that builds and runs a team of Agents. They answer and make calls in any language the caller speaks, chat on WhatsApp, read and send email, and keep contacts, tasks and orders. This skill teaches you how to work in a AgentWaves workspace through its MCP server.

## Connect

- Server: `https://agentwaves.net/mcp` (Streamable HTTP).
- Sign in with OAuth when your app supports it. The user picks the workspace and chooses **read only** or **read and act**.
- Otherwise send an API key the user created in AgentWaves under **Developers**: `Authorization: Bearer <key>`.
- Tool list and input schemas: `https://agentwaves.net/mcp/tools.json`.
- Without MCP, the same actions are a REST API at `https://agentwaves.net/api/v1` (same key, same rules). Spec: `https://agentwaves.net/api/v1/openapi.json`.

## Start every session the same way

Call `get_started` first. It returns the workspace, plan, Agents, phone numbers, the last 7 days of activity and what this connection may do. Use the names it returns; never guess Agent names or IDs.

## Reading

| Need | Tool |
| --- | --- |
| Agents and whether they are on | `list_agents` |
| Recent calls, filtered by Agent, direction, number or days | `list_calls` |
| One call with summary, extracted details and transcript | `get_call` |
| Find a person by name, phone, company or tag | `find_contacts`, then `get_contact` |
| Follow-ups from calls, WhatsApp, email and orders | `list_tasks`, `get_task` |
| Outbound campaigns | `list_campaigns` |
| What an Agent knows about the business | `search_knowledge` |
| Where an ordered call is now | `order_progress` |

Summarise; do not paste whole transcripts unless asked. Quote phone numbers in international format (for example +14155550123).

## Acting (needs read and act access)

| Action | Tool |
| --- | --- |
| Have an Agent call someone now or later | `order_call` |
| Write what happened on a task | `add_task_note` |
| Mark a task open, in progress, done or dismissed | `set_task_status` |
| Fix a contact's details or put them on do-not-call | `update_contact` |
| Turn an Agent off or back on | `set_agent_on` |

Rules:

1. **Confirm before you act.** Before `order_call`, read back the Agent, the number, what the Agent should achieve and when, and wait for a clear yes. Do the same before changing data or turning an Agent off.
2. **Respect consent.** Never order a call to a contact marked do-not-call. If the workspace requires approval, the call waits for the owner in AgentWaves; tell the user so and follow it with `order_progress`.
3. **Write the task for the Agent.** `task` is what the Agent should get done on the call, in plain words: who it is talking to, why, and what a good outcome is.
4. **Follow through.** After an ordered call ends, offer the summary from `order_progress` and add a task note if something is still open.

## Privacy

Results contain customer data. Share them only with the user you are working for, and do not store them elsewhere unless the user asks. Every action you take is recorded in the workspace audit log under the user's name.

## Errors

- *Not allowed*: the connection is read only, or the user's role cannot do this. Say so and suggest reconnecting with read and act, or asking a workspace admin.
- *Not found*: search again with `find_contacts`, `list_agents` or `list_tasks` instead of guessing IDs.