No user-submitted related servers found.
Scored across 20 tools
Each tool targets a clearly distinct resource or action: fleet overview, agent list, agent detail, services, processes, event log, checks, history, software, updates, tasks, clients/sites, alerts, scripts, pending actions, logs, and server info. Even the status-related tools (fleet_overview, list_alerts, pending_actions) are separated by scope and description.
All tools share the trmm_ prefix, but the convention after that is inconsistent: some use list_/get_ verbs, others use bare agent_* resource names, and trmm_api_get puts the verb at the end. The names are still readable and grouped by resource, but the pattern is not uniform.
At 20 tools this sits in the heavy range, though the RMM domain is broad and most tools cover a distinct resource type. Some agent read tools could potentially be consolidated, but the count is not unreasonable for the breadth of data exposed.
The read/diagnostic side is well covered: fleet health, agent inventory, processes, event logs, software, updates, scripts, alerts, and logs. However, the script lifecycle is incomplete because trmm_list_scripts explicitly references trmm_run_script, yet no run/create/update/delete script tool exists, and the management/action side of an RMM is largely absent aside from a GET-only API escape hatch.