Related Servers

Every tool targets a distinct aspect of spatial world modeling: entity CRUD, querying, relations, map generation, simulation, observation ingestion, view prediction, goal linking, outcome recording, spatial specs, evidence packs, blackboard coordination, snapshot management, game input generation, and state waiting. There is no ambiguity between operations like update_entity vs record_outcome vs ingest_observation—each has a clear and separate purpose.

All tools follow a consistent verb_noun snake_case pattern (e.g., update_entity, query_entities, set_relation, get_spatial_map, simulate_movement). Verb choices vary appropriately with their actions, but the style and structure are uniform across all 15 tools, making the set predictable and easy to navigate.

15 tools is well-scoped for a rich domain like spatial world modeling. Each tool covers a distinct feature area without redundancy, and the count remains within the ideal range for a comprehensive MCP server. The number feels justified given the breadth of functionality (state management, simulation, spatial reasoning, evidence, collaboration, and automation).

The tool surface covers the full lifecycle: entity creation/update (update_entity), querying (query_entities), deletion and post-action updates (record_outcome), relationships (set_relation), spatial mapping (get_spatial_map), simulation (simulate_movement), observation ingestion (ingest_observation), expected view (get_expected_view), goal integration (link_to_goal), compliance (manage_spatial_spec), evidence (create_evidence_pack), multi-agent coordination (use_spatial_blackboard), snapshot/history (manage_snapshot), game input generation (generate_game_inputs), and waiting for state changes (wait_for_spatial_state). No obvious gaps prevent an agent from performing critical workflows.