No user-submitted related servers found.
Scored across 77 tools
Many retrieval tools overlap heavily (memory_recall, memory_search_fast, memory_associate, memory_recall_iterative, memory_context_build, memory_answer, memory_temporal_query) and save variants blur (memory_save vs memory_save_fast vs memory_observe vs memory_episode_save). Descriptions add nuance, but an agent can easily misselect among these clusters.
Nearly all names use snake_case and many carry domain prefixes (memory_, kg_, workflow_, self_), but conventions are mixed: prefix_noun (memory_save), verb_noun (save_intent, classify_task), and bare verb/noun (analogize, benchmark, file_context). Still readable, but not a predictable pattern throughout.
77 tools is far beyond a well-scoped memory server; many are eval, debug, perf, or internal admin utilities that could be consolidated. This creates severe surface bloat and high selection cost.
Core lifecycle is well covered: save/update/delete/recall/history/export/forget/consolidate plus graph, episodes, skills, rules, and sessions. Minor gaps exist (e.g., no explicit import counterpart to export, some tools are eval/admin rather than user-facing memory operations), but core workflows have no dead ends.
