No user-submitted related servers found.
Scored across 35 tools
Most tools are clearly separated by resource area (queue, view, build, node, plugin) and follow get_all_X/get_X pairs. Some ambiguity remains between the generic item tools and job-related operations, and the plugin update/backup/problem variants could be confused, but the descriptions mostly clarify the boundaries.
Tool names consistently use snake_case verb_noun patterns, with get_all_<resource>/get_<resource> pairs and set_<resource>_config throughout. Minor deviations like query_items or run_groovy_script still fit the verb-first convention and do not break the overall predictability.
At 35 tools, this is well above the 25-tool threshold and feels heavy for an agent to navigate. Many near-duplicate accessor pairs and plugin variants inflate the surface without adding proportionally distinct functionality.
The operational coverage is strong: builds, artifacts, console output, test reports, queue management, nodes, plugins, and pending-input handling are all represented. However, lifecycle operations are incomplete—there is no explicit create/delete for jobs, nodes, or plugins, and no plugin install/update—so administrative workflows hit dead ends unless falling back to run_groovy_script.