You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 28, 2026. It is now read-only.
speedyrulz edited this page Oct 28, 2026
·
1 revision
Extra Tools (MCP)
Tool servers you set up in RulZ LLM Suite (on its MCP page, saved in %APPDATA%\RulZ LLM Suite\mcp.json) work in the Coding Agent too, with nothing to set up twice. An example is REA for reverse engineering.
Settings → Extra tools lists them and shows whether each is running. Start now starts them. Otherwise they start the first time the agent needs one.
Ask for them by name: "use REA to study the app in C:\Apps\Viewer".
How tools are offered
Some servers have hundreds of tools (REA alone has 207, about 240K tokens of descriptions), so none are sent up front. Instead, the model gets two tools:
find_tools searches the available tools by keyword.
load_tools loads the ones it needs, which are offered from the next step.
Loaded tools may use 15% of the context. When they'd go over that, the oldest are unloaded first. The servers' own advice to the model is added to the system prompt.
Approvals
A server's ordinary tools ask once per task, with an Allow for this task option.
Tools the server marks as destructive (running or instrumenting programs, installing to a phone, and so on) ask separately, every time.
Hands-off skips the question only for ordinary tools.