Related Servers

Most tools have distinct resource/action pairs, and the high-level prefixes (world_, shape_, map_, mod_, batch_) make the primary purpose clear. However, a few clusters blur together—omni_errors/omni_logs/omni_notifications all address log inspection, and omni_map_guide/omni_map_onboard/omni_map_docs/omni_knowledge are all informational—so an agent may occasionally pick the wrong one. Detailed descriptions save it from a lower score.

The set consistently uses the omni_ prefix and lowercase snake_case, and the omni_<domain>_<detail> pattern is recognizable across world_, map_, mapdev_, shape_, mod_, and batch_ tools. The pattern is not strictly verb_noun: one-word tools like omni_state, omni_inventory, and omni_chat mix with action-style names like omni_world_create and omni_recipe_validate. This is a minor inconsistency but not chaotic.

51 tools is far beyond the 25+ threshold and lands in the 50+ extreme-mismatch range for this rubric. The server covers a broad Minecraft bridge surface, but the sheer number of entries will overwhelm tool-selection and make coherent orchestration harder. Clusters like logs/notifications/errors and the many map_* document tools could be consolidated.

The tool surface covers the full map-development workflow: world lifecycle, batch validate/apply, shape generation, dev/play mode, mod staging, recipe linting, verification reports, and the map agent context pack. Minor gaps exist—no world delete, no mod list/remove, and no explicit undo/rollback for batches—but those are workaroundable via omni_command or the existing ledger/report machinery. Overall, the core domain is well covered.