Tools & toolsets
About 4 minutesUpdated August 2026
Every Qalyb MCP tool, grouped into toolsets you can enable per connection, and the guardrails they all follow.
| Toolset | What it does | Tools |
|---|---|---|
| core | Identity, members, plan & usage. | whoami, list_members, get_usage_summary |
| agents | Build and manage agents. | list_agents, get_agent, create_agent, update_agent, list/restore prompt revisions, delete_agent, get/set escalation policy, list templates, personas, voices |
| conversations | Calls, chats, transcripts, recordings, exports. | list_calls, search_transcripts, get_call, get_call_recording, get_call_execution_log, start_outbound_call, delete_calls, exports |
| tickets | The human-handoff inbox. | list_tickets, get_ticket, claim_ticket, assign_ticket, reply_to_ticket, resolve_ticket, reopen_ticket, add_ticket_note, set_ticket_status, set_ticket_priority, create_ticket |
| analytics | Timezone-aware performance metrics. | get_analytics_overview, get_call_analytics, get_agent_analytics, get_campaign_analytics, get_chat_analytics |
| campaigns | Outbound voice / WhatsApp at scale. | list_campaigns, get_campaign, create_campaign, add_campaign_contacts, cancel_campaign, list_campaign_calls, retry_campaign_call |
| knowledge | RAG knowledge bases and documents. | list_knowledge_bases, create_knowledge_base, list/add documents, query_knowledge_base, delete document / base |
| components | The UI components your agents render in chat. | list_components, get_component, create_component, update_component, clone_component, archive_component |
Guardrails
- Destructive actions confirm first. Deleting an agent or cancelling a campaign without
confirm: truereturns a preview (including deletion impact) instead of executing. - Prompt edits are reversible.
update_agentreplaces prompt text by default — passprompt_mode: "append"to add to it instead. A replace that would cut the prompt to under a third of its length needsconfirm_replace: true, and every change from any surface is snapshotted, sorestore_agent_prompt_revisioncan put the old prompt back. - Shared templates stay shared. The global component gallery is readable and clonable from your workspace but never editable through it —
clone_componentgives you your own copy to change. - Names work everywhere. Tools accept agent, member, and knowledge-base names — not just ids — and disambiguate when several match.
- Workspace isolation. Every tool is scoped to the authenticated workspace; other organizations' data is invisible.
- Plan limits speak up. Hitting a plan gate returns a clear upgrade message rather than a cryptic error.
Building an integration in code instead? The same operations are on the REST API.
Was this guide helpful?