Scored across 55 tools
Tools are grouped around distinct resources—cases, folders, collections, executions, launches, releases, external links, and analytics—and the descriptions explicitly call out near-misses like test collections vs executions and launch statistics vs launch trends. A few pairs such as add_cases_to_collection vs add_cases_to_execution still need careful reading, but every tool has a distinct purpose.
Naming is consistently verb-first snake_case with standard CRUD verbs: get/list/create/update/delete/add/remove/link/link. Even compound tools like bulk_update_cases, run_health_check, and report_case_result follow the same readable pattern with no style mixing.
55 tools is far beyond the 3–15 well-scoped range and clearly falls into the too-many category, even though the underlying domain is broad. The count will overwhelm agents during tool selection and makes the server hard to use effectively.
Major lifecycle coverage is strong: cases, folders, suites, collections, executions, releases, launches, external links, and reports all have meaningful create/read/update/delete or equivalent workflows. Minor reverse-operation gaps exist—such as no unlink for autotest-to-case and no way to remove a single loose case from an execution group—but agents can generally work around them.