Settings: Tools
Tools settings control how Row-Bot exposes enabled external capabilities to the model, its search and retrieval helpers, the small built-in tools it can use, and the custom tools you add.

Where To Find It
Open Settings, then choose Tools in the Capabilities group, or search for it with Find a setting.
Capability Loading
- Only the ones a request needs (recommended) lets Row-Bot search enabled MCP, plugin, Custom Tool and channel capabilities when a request needs them. The tools Row-Bot uses all the time (pages, questions, helpers, the shell and background processes, workflows, memory and the web) are always there; rarely used built-in ones, such as the tracker, video editing and the updater, are found the same way as app tools.
- All of them, every time is the eager compatibility mode. It sends every enabled external schema allowed by the current provider and policy, which can consume more context.
Both modes preserve tool enablement, provider compatibility, Agent Profile restrictions, workspace policy, approval gates, prompt-injection handling, and execution budgets.
Search & Knowledge Tools
Search & Knowledge Tools enables or disables configured research and reference tools such as arXiv, DuckDuckGo, Tavily web search, Wikipedia, Wolfram Alpha, and YouTube. Provider-specific setup fields store the credentials required by optional search services.
Built-In Tools
Built-in tools are small tools for everyday tasks, such as the calculator, weather, charts and the URL reader. Each has its own switch, and the heading counts how many are on. These used to be a separate Utilities page. Developer tools are among them; the command palette can turn them on ("turn on developer tools").
Custom Tools
Custom tools turns a folder's scripts into tools Row-Bot can run. Add from a folder (in the desktop app) inspects the folder and drafts the tool; this sends short excerpts of the folder to your chosen model, which may cost money with a paid provider. You can also ask Row-Bot in a chat to make a tool from a repository, or use the Custom Tool Builder in a code folder's Developer panel. Review a custom tool's commands before turning it on.
Recommended Workflow
- Keep Only the ones a request needs for normal use.
- Enable only the search and integration tools you intend Row-Bot to use.
- Confirm external services are healthy before relying on them.
- Use eager mode temporarily only when testing compatibility with an older model or integration.
- Review approvals before any action that writes, sends, or changes external state.
What Is Saved
The capability-loading choice and tool settings are local global preferences. Per-task skill activation is stored separately and does not change this tool policy.
Privacy And Safety
Auto mode reduces schemas in the model prompt, but it does not make a networked tool local. When Row-Bot actually calls a hosted model, remote MCP server, plugin service, account integration, or channel, the data required by that operation can leave your machine. Disabled or profile-denied tools are not made available by discovery.
Troubleshooting
- If an external tool is not found, check its app in Settings › Apps, its Custom Tool or channel configuration, and the active Agent Profile.
- If a direct tool worked previously but discovery does not select it, use a precise prompt and inspect Row-Bot Status for effective tool groups.
- If a provider rejects tool schemas, choose a compatible tool-capable model or temporarily test eager mode.
- If search results are noisy, turn off the search tools you don't need.
For the full runtime model, see Progressive Tools And Skills.