Tools: what your assistant can do
Your assistant can only do in Botize what the tools of your MCP allow. Some come built in; the ones that act on your apps you add yourself, one by one.
Built-in tools
Every new MCP comes with tools to work with your tasks and the catalog:
- See your tasks, read how each one is built and check its run history.
- See which app accounts you have connected in Botize.
- Search the catalog for apps and actions, and read the Botize documentation.
- Create new tasks. They're created paused, so you can review them before switching them on.
- Modify, switch on, pause and reschedule your tasks.
- Ask you for a new tool (see below).
Using these tools uses no operations. Botize currently offers no tool to delete tasks: you do that from the dashboard.
Tools from your apps
Your assistant can also use specific actions of the apps you've connected: send a Telegram message, publish to a social network, add a row to a spreadsheet…
- Each action is a separate tool, and you approve each one. A whole app is never granted at once.
- The tool needs an account of that app connected in Botize. Profiles and connected accounts
- Each use uses one operation, even if the action fails.
How a tool gets added
- You ask for something your assistant can't do yet, for example: "post this text to my Telegram channel".
- Your assistant finds the action in the catalog and asks for permission. It gives you a link to MCP connections. The link opens that panel in Spanish; you'll find it in English at botize.com/en/mcps.
- Open the link. You must be signed in to Botize with the same account as the MCP. Under Requests from the agent you'll see which action it wants and the Reason it gives.
- Decide what it can send, field by field, and with which account (see below).
- Click Approve, or Reject if you don't want to grant it.
There's no message when you approve: the screen refreshes and the tool appears in your MCP's list. Some assistants don't see it until you refresh their list: Your assistant can't see new tools.
Decide what it can send, field by field
When approving a tool you see its fields (the message text, the channel, the image…). For each one you choose:
| Option | What it means |
|---|---|
| Open to the AI | Your assistant decides the value each time it uses the tool. |
| Fixed value | You set the value. That value is always sent, and your assistant never sees it. |
| Do not send | That field isn't sent at all, not even empty. Only available for optional fields. |
By default, required fields are Open to the AI and optional ones are set to Do not send.
A fixed value is sent exactly as written: if you type something in braces, such as {{title}}, nothing is substituted.
For example, to let your assistant post to one channel and no other: leave the text Open to the AI and set the channel as a Fixed value.
Which account
If you have several accounts of the same app connected, you can:
- Fix one account: the tool always uses that one.
- Leave it open: your assistant picks, on each use, among your connected accounts of that app. Any other value is rejected.
One tool per action
An MCP has at most one tool per action. If your assistant asks again for an action it already has, the request opens anyway, and approving it replaces the previous one with the fields and account you choose now. In MCP connections you'll still see a single tool for that action.
Remove a tool
You currently can't remove a single approved tool from an MCP. You have two options:
- Change what it can send: ask your assistant to request it again and approve it with different fields or a different account. It replaces the previous one.
- Remove them all: revoke the connection and connect again with a new MCP, where you approve only the tools you want.