No user-submitted related servers found.
Scored across 102 tools
Most tools are cleanly separated by resource type, but heavy overlap exists among the high-level monitoring summary tools (get_infrastructure_health, get_critical_issues, get_system_overview, get_last_24_hours_summary, get_actionable_items, get_performance_alerts), which all effectively return problem/issue summaries. Additionally, get_history, get_trends, get_item_history_range, and get_latest_data have overlapping data-retrieval purposes that could cause misselection.
The predominant pattern is zabbix_verb_resource_model, but deletion verbs mix singular and plural forms inconsistently (e.g., zabbix_host_delete vs. zabbix_delete_hostgroups, zabbix_delete_users). Create/update/delete verbs are also not uniformly positioned across resources, making the naming pattern harder to predict.
With 102 tools, this is an extreme over-expansion of the tool surface. While Zabbix is a broad platform, many CRUD operations could be consolidated or generated dynamically; this volume will overwhelm agents and increase selection errors.
The set covers the vast majority of Zabbix resource CRUD operations (hosts, items, triggers, templates, maintenance, users, media types, actions, maps, dashboards, proxies, services, discovery rules) plus import/export and health summaries. Minor gaps exist, such as missing update/delete for user groups, write operations for user media, and update support for correlations, but these are workable gaps.