Scored across 13 tools
Most top-level tools target a distinct resource (database, map, event, system, image), but analyze_project overlaps with get_project_context and query_database/query_map for project summaries, validation, and usage lookups. The detailed view/action parameters help, but an agent could reasonably call the wrong tool when asking broad project questions.
All tool names follow a consistent verb_noun snake_case pattern, which is predictable and readable. Minor inconsistencies exist: query_database uses a shorter noun than create/update/delete_database_entry, and manage_map_event vs edit_map slightly blurs the map/event boundary.
13 tools is a well-scoped count for a project with analysis, database CRUD, map generation/editing, event management, and system configuration. Each tool earns its place even though analyze_project is quite overloaded with sub-modes.
The server covers the core lifecycle well: database entries are fully CRUD-able, events are create/read/update/delete, maps are create/read/update, and system settings are readable/editable. Minor gaps include no map deletion, no explicit common-event creation, and event commands being append-only rather than fully editable.