No user-submitted related servers found.
Scored across 12 tools
Most tools have clearly distinct roles: discovery (list_services), introspection (describe_service vs describe_operation differ by granularity), connectivity (check_service), and invocation split cleanly by protocol (soap_call vs rest_call). The main soft overlap is run_scenario vs run_test_suite (single file vs folder/tags) and check_last_response vs scenario assertions, but descriptions make the boundaries explicit enough to choose correctly.
The set is predominantly consistent snake_case verb_noun (list_services, describe_operation, check_service, validate_scenario, run_scenario, reload_config). Minor deviations exist: soap_call/rest_call use protocol-first ordering and session_variables is a noun-only name with no verb, but the pattern remains readable and predictable.
At 12 tools the server is well-scoped for an API/service testing surface, with each tool mapping to a distinct phase (discover, describe, check, call, validate, run, inspect, reload). Nothing feels redundant or missing at the count level.
The lifecycle is largely covered: discovery, schema introspection, connectivity checks, SOAP/REST invocation with variable extraction, assertion probing, scenario validation and execution (single and suite), plus config reload. Gaps are minor: no tool to list/discover available scenario files or suites, and no built-in scenario authoring/write operation, so agents must rely on external file access.