Skip to main content
Once connected, the agent operates on your company data through a catalog of tools. Every tool runs the exact same query or command the admin panel runs, so the two surfaces cannot diverge in behaviour. Before operating, the agent can call woku_guide, which returns woku’s method and playbooks (from an intent to the sequence of tools), and design_voc_program, which proposes a listening program for your customer journey.

Tools by family

The server exposes 143 tools organized by family: With this, an agent can design a listening program, summarize last week’s reviews, compare NPS across locations, run a report, review goal compliance, approve an action plan, or create a tracker, all from the conversation.

Toolsets

The catalog is large, so a connection can narrow it. Adding ?toolsets=nps,clients (comma-separated) to the MCP endpoint URL exposes only those families; without the parameter, or with ?toolsets=all, everything is exposed. The guide, company, and search families are always available. The search and fetch tools follow ChatGPT’s deep research contract: search searches across all company data and fetch brings the detail of a result.

Read and write

Connections handle two permissions: mcp:read to query data and mcp:write for the tools that create, edit, or delete. Read tools work with mcp:read alone; write tools also require mcp:write, and destructive ones (for example delete_woku) or sends (for example send_nps_invitations, send_report_now) additionally require confirm: true in the call, so nothing is deleted or sent without an explicit confirmation. If the connection does not have the mcp:write permission, the write tools respond with an error indicating so and the rest keep working normally. The list of tools the server advertises on a live connection (tools/list) is always the authoritative answer about what is available.