No user-submitted related servers found.
Scored across 8 tools
The two domains (human memory vs. project idea map) are clearly separated, and remember/forget/map_add/map_resolve each target a distinct operation. The only mild overlap is between get_rules, get_profile and where_is_my_data, which all return loosely related read-only context and could be confused by an agent looking for stored knowledge.
There is a readable grouping (get_* for reads, map_* for map operations), but conventions are mixed: bare verbs (remember, forget), verb_noun (get_profile, get_map), noun_verb (map_add, map_resolve), and a full sentence (where_is_my_data). An agent can follow it, but it is not a predictable pattern.
Eight tools is well within the sweet spot and each one maps to a concrete operation: read rules/profile/map, write/remove a fact, add/resolve a map node, and locate data. Nothing feels redundant or padded.
Fact memory covers create, read and delete, but there is no update/edit of an existing fact, and the map surface lacks any node removal, rename or edit operation — only add and resolve. An agent that mis-records a node or needs to correct a preference will hit a dead end.