No user-submitted related servers found.
Scored across 27 tools
The tools are organized by clear buyer-side, seller-side, wallet, and wave roles, so most choices are obvious. A few pairs share payment/status/file-delivery concerns—buy_offer vs pay_invoice, check_payment vs get_receipt, download_files vs receive_file—but the descriptions give enough context to distinguish them.
The dominant convention is lowercase snake_case verb_noun, which makes command intent predictable. Minor noun-phrase exceptions like my_offers and wallet_status, plus the compound setup_wallet, are the only inconsistencies.
27 tools exceeds the 25-tool threshold for a heavy surface and bundles three distinct subsystems: offer/invoice commerce, wallet configuration, and wave messaging. Several adjacent operations could be merged, so the count feels inflated even though the underlying product is broad.
The offer lifecycle is covered end-to-end: create, attach, activate, search, buy, pay, download, renew, add capacity, and delete, with a parallel invoice path and a full wave messaging/file-transfer flow. No obvious dead-end workflow remains for the stated capabilities; missing behaviors like refunds are explicitly designed out of the product.
