No user-submitted related servers found.
Scored across 163 tools
The tool set has several dense clusters that are hard to tell apart: land_deed_by_plot and land_deed_by_uid accept effectively the same selector, market_status/active_status/completed_status overlap, and the rental_offers/rentals_by_player/rentals_v3_by_* family is highly confusing. The long descriptions help only after the agent has read them; names alone frequently point at more than one plausible tool.
Tool names are uniformly lower_snake_case and consistently use a domain prefix such as market_, player_, land_, collector_, tournament_, or guild_. Minor exceptions like list_endpoints and describe_endpoint, plus a few long phrase-based names, keep this from being a 5, but the general pattern is predictable and readable.
163 tools is an extreme agent-facing surface, even for a broad public API. Many near-duplicate variant routes could be consolidated into parameterized tools, so the count creates unnecessary decision burden rather than a well-scoped toolset.
For a deliberately read-only public API server, the coverage is remarkably thorough: cards, players, markets, land, tournaments, guilds, battles, conflicts, proposals, and chain transactions are all represented. No obvious domain gap or read workflow dead-end appears within the stated read-only scope.