No user-submitted related servers found.
Scored across 2 tools
The two tools are clearly differentiated: screen_name handles one name, while screen_batch handles up to 50 names in a single call. Their descriptions explicitly state the scope and endpoint, leaving no plausible confusion about which tool to use.
Both names follow a consistent snake_case pattern with the shared `screen_` prefix. The suffixes distinguish single-name versus batch operations predictably.
Two tools are reasonable for a narrow screening API, with a clean single-versus-batch split. However, the surface is quite thin and could feel limited if agents expect quota checks or a way to retrieve prior screening results.
The core screening workflow is covered for both individual and bulk names, including result bands and top matches. Minor gaps remain, such as checking remaining quota, retrieving a prior screening by ID, or handling batch status separately.
