No user-submitted related servers found.
Scored across 185 tools
Many tools have overlapping purposes that even their verbose descriptions struggle to separate: eight-plus rental tools (rental_offers, rental_bids, rentals_v3_by_player, rentals_v3_by_role, rentals_by_bid, rentals_by_player, rental_offers_by_player, rental_bids_by_player), three market status tools (market_status, market_active_status, market_completed_status), and parallel ranked_draws_* vs frontier_draws_* sets with nearly identical names. An agent choosing between these will routinely misselect without reading pages of caveats.
The overwhelming majority use snake_case with a domain prefix (land_, player_, market_, guild_, tournament_, cards_, rental_, conflict_), which is predictable. A few outliers exist (transaction_inspect, list_endpoints, describe_endpoint) and the domain prefixes vary (player_, vapi_market_, rentals_ vs rental_), but the convention is broadly readable.
185 tools is an extreme mismatch for any single server's purpose, far beyond the typical 3-15 well-scoped range. Even a comprehensive read-only API wrapper does not justify this volume, and the redundancy (multiple tools per underlying route or near-equivalent route) shows many tools do not earn their place.
The surface covers a very wide domain set — accounts, balances, land, market, rentals, guilds, tournaments, battles, cards, collectibles, draws, proposals — with mostly read-only lifecycles fully represented. Gaps are minor (mostly mutation/claim operations deliberately omitted), and coverage is arguably over-, not under-, complete.