No user-submitted related servers found.
Scored across 9 tools
Most tools have clearly distinct roles: catalog lookup, connection-point inspection, regime classification, Tier-1 screening, Tier-2 AC study, mitigation proposal, end-to-end triage, and capacity sweep. There is some overlap between `screen_connection_application` and manually chaining `run_tier1_screen` / `run_tier2_ac_study`, and `search_tools` is a meta-tool that stands apart from the domain workflow, but descriptions make the progressive-fidelity boundaries understandable.
All tools use snake_case with a clear verb-first pattern such as `list_networks`, `inspect_connection_point`, `classify_screening_regime`, `run_tier1_screen`, and `propose_mitigations`. Tier and domain qualifiers are used consistently enough that the naming remains predictable.
Nine tools are well scoped for a grid-screening server, with each covering a distinct stage from catalog discovery through screening, detailed study, mitigation, end-to-end triage, and capacity sweep. The set is neither thin nor bloated.
The surface covers the core lifecycle: network catalog, PCC inspection, regime classification, fast and detailed screening, mitigation synthesis, end-to-end application screening, and hosting-capacity sweep. Minor gaps remain around explicit artifact/result retrieval or standalone audit/export operations, though the end-to-end tool returns audit receipts and resource URIs.