No user-submitted related servers found.
Scored across 7 tools
dry_run and start_run perform the same operation (sync vs async) and get_result is tightly coupled to start_run, but the descriptions make the relationship and polling flow explicit. run_checks could be mistaken for dry_run, yet its description clearly states it reuses an already-running lab without deploy/destroy. Boundaries are mostly distinct with only this intended pairing overlap.
Six of seven names follow a verb_noun pattern (dry_run, start_run, get_result, run_checks, record_baseline, check_types). 'validate' is a bare verb, a minor deviation, but the overall convention is predictable and readable.
Seven tools is well-scoped for a dry-run validation server: a synchronous path, an asynchronous path with polling, a re-check tool, baseline generation, and two lightweight metadata/introspection tools. Each earns its place.
Core lifecycle (validate, dry_run, async run + poll, run_checks, record_baseline, check_types) is covered, but the keep_lab=true flow explicitly tells the agent to 'destroy the lab' afterward and there is no destroy_lab or list_runs tool to do so. That is a notable dead end in a workflow the descriptions actively encourage.