No user-submitted related servers found.
Scored across 17 tools
Product prefixes (fastbcp_, fasttransfer_, lakexpress_, migratorxpress_) clearly scope each tool, and preview/execute pairs are well distinguished by the confirmation gate. The four near-identical *_info tools and the overlap between search_docs, the per-product info actions, and arpe_release_notes create some informational overlap, but the prefixes resolve most confusion.
The core verb_noun pattern (preview_export, execute_export, preview_command, execute_command) is consistent and readable. However the noun choices diverge by product (export/command/transfer) for the same conceptual action, and the shared tools mix conventions: arpe_get_status, arpe_quick_start, arpe_release_notes are prefixed while search_docs is not.
17 tools is reasonable for a set covering four distinct CLI products plus shared utility tools, and each tool has an evident purpose. It is on the heavier side and the replicated *_info tools add some redundancy, but nothing feels like pure filler.
Each product gets a build→confirm→execute lifecycle plus info, which covers the core command-building workflow end to end. The main gap is asymmetric: migratorxpress_validate_auth_file has no counterpart for FastBCP/FastTransfer/LakeXpress, which also consume credentials, leaving agents without early validation for three of the four products.