No user-submitted related servers found.
Scored across 72 tools
The tool set is organized by clear resource domains and descriptions are detailed, but several pairs overlap (pws_get_titles vs pws_get_championships, pws_execute_action vs the purpose-built create_storyline/award_championship/sign_worker tools). With 72 entry points, an agent faces real misselection risk despite coherent naming.
Virtually all tools use the pws_ prefix, lowercase snake_case, and familiar verb_noun patterns such as pws_get_*, pws_create_*, pws_update_*, and pws_set_*. A few noun-style names (pws_company_overview, pws_database_catalog, pws_contract_advice) and bare verbs (pws_search, pws_query) keep this from a perfect 5.
At 72 tools, the server is far beyond even the 'heavy' range and into a scale that is harmful for agent tool selection. The breadth may mirror game features, but many tools could be consolidated or parameterized; this count is an extreme mismatch for a coherent MCP surface.
Coverage is impressively broad: roster, contracts, hiring, shows, segments, storylines, titles, stables, tag teams, brands, events, venues, commentary, promises, network deals, auditing, and raw SQL fallback are all represented. Minor gaps remain around network-deal negotiation and some advanced worker interactions, but pws_execute_action and query tools provide workarounds.