No user-submitted related servers found.
Scored across 11 tools
Most tools are clearly separated by resource type, such as build details, errors, tests, coverage, and dynamic analysis. However, get_dashboard and get_project_overview both provide project-level aggregate status, and get_failing_tests overlaps somewhat with get_build_tests with a failure filter, creating minor ambiguity.
All tools follow the get_<resource> pattern consistently, making the set highly predictable. The names clearly indicate both the action (get) and the target (dashboard, build, coverage, tests, etc.).
With 11 tools, the count is well within the ideal range for a domain-specific read-only CDash server. Each tool covers a meaningful slice of the dashboard/build/test/coverage surface without unnecessary duplication.
The tool set covers the main CDash read workflows: dashboards, build details, test results, errors, coverage, dynamic analysis, configure output, and VCS update info. The main gap is project discovery—there is no way to list available projects, so agents must already know the project name.