Related Servers

The three browser-related tools (check_app_in_browser, probe_page, trigger_crawl) have clearly drawn boundaries, with probe_page explicitly documenting what it is NOT for. Minor overlap remains between test_suite's "results" action and executions lookups, and between test_suite/test_case, but action schemas make the targets distinguishable.

Two conventions coexist: verb-first snake_case tools (check_app_in_browser, probe_page, trigger_crawl) and bare singular nouns multiplexed by an "action" parameter (test_suite, environment, project, test_case). "executions" is plural where the other noun tools are singular, adding another small inconsistency, though all names are readable and snake_case throughout.

Eight tools for a QA/test-automation platform is well scoped, with CRUD-ish domains sensibly collapsed into action-multiplexed tools rather than exploded one-per-operation. Each tool maps to a distinct capability area (test management, environments, live checks, probing, crawling, history, projects).

There is no tool to actually run or trigger a test suite — executions references "test-suite runs" in history, but the surface can only create/update/delete cases and suites, leaving a dead end for the main workflow. project also lacks update/delete (documented as web-app-only) and test_suite lacks update, though environments and executions are well covered.