Assistant CoreAssistant Core
Tools & MCP

Built-in Tools

Built-in Assistant Core tools and when the assistant uses them.

Built-in tools are capabilities that come with Assistant Core. You do not need to configure your own endpoint; enable the related assistant feature when the admin UI provides a toggle.

Available Tools

ToolUsed forNotes
Knowledge BaseQuestions about uploaded documents or crawled websitesThe assistant can search documents, list documents, search by file name, and read specific files
MemoryRemembering or recalling information about a userCan search, add, update, or delete memories depending on context
WebCurrent information, web pages, places, research papers, images, or videosSupports web search, URL scraping, maps, scholar search, image search, video search, and lens-style analysis
Image GenerationCreating or editing images from user requestsAvailable in chat; generated images are returned directly in the conversation
MusicVoice requests to play musicUsed in voice sessions; can play a named song or a random song
End ConversationVoice requests to end the conversationThe assistant says goodbye and closes the voice session

Deep Research exists in the system but is not currently enabled as a default chat or voice tool.

Enable Or Disable Features

  1. Open the Admin Dashboard.
  2. Select the assistant you want to configure.
  3. Go to Assistant Settings.
  4. In Features, enable or disable capabilities such as Knowledge, Web Search, Memory, Voice, File Upload, or MCP.
  5. Click Save Changes.

When Does The Assistant Call A Tool?

The assistant decides to call a tool when the request needs extra data or an action. For example:

  • A question about internal documents usually uses Knowledge Base first.
  • A question about fresh information or a specific URL uses Web.
  • A request to create an image uses Image Generation.
  • A voice request like “play...” or “end the call” uses the matching voice tool.

Prompting Tip

If you want the assistant to prefer a tool, say that in the system prompt. For example:

When the user asks about company policy, always search the Knowledge Base before answering.
If the Knowledge Base has no relevant information, say that clearly.

Avoid forcing web search for every question. It can make replies slower and may use external data when the assistant already has enough context.

On this page