No user-submitted related servers found.
Scored across 190 tools
Despite extremely detailed descriptions, many tools have near-identical surfaces: ranked_draws_* and frontier_draws_* mirror each other across six tools each, land_resources_balances_history vs _history_window vs _history_count blur together, and land_deed_by_plot / land_deed_by_uid / land_deeds_bundle / land_deeds_search / land_deeds_owned overlap heavily. The rental family (rental_offers, rental_offers_by_player, rentals_by_player, rentals_v3_by_player, rentals_v3_by_role, rentals_by_bid) requires reading several paragraphs to tell apart, and cards_collection vs cards_find vs cards_get_details also collide.
Everything is snake_case, which helps, but the scheme is noun-prefixed resource families with inconsistent internal shape: some are verb-final (cards_max_land_pp, land_volume, land_regions_counts) and others are verb-first after the prefix (player_balances, market_query_by_card). Prefixes also mix vapi_market_, market_, and land_liquidity_* for closely related routes, so an agent cannot reliably guess a name from an intent.
190 tools is far beyond a workable set for an agent to reason over, and much of the bulk is 1:1 mirroring of upstream REST routes (six ranked-draw tools, six frontier-draw tools, dozens of land-resource list/count pairs). Many could be collapsed into parameterized tools (e.g. one draw tool with a draw_type, one history tool with a mode).
The surface is very broad, covering cards, land, market, battle, tournament, guild, conflict, rental, delegation, collector, and governance domains with list/count/history variants. The notable gap is that the server is strictly read-only, which appears intentional, but there are also no aggregation/total tools and many routes leave pagination as a dead end, forcing workarounds.