No user-submitted related servers found.
Scored across 5 tools
Each tool has a fairly distinct role: bulk read (batch_inspect), search (find_by_intent), deep read of one script's logic (get_phase_map), sync/index (sync_codebase), and write (enrich_knowledge). The only mild overlap is between batch_inspect and get_phase_map, since both return stored knowledge about code, but the granularity difference (identity cards vs. execution phases) is stated clearly enough to choose correctly.
All five tools share a clear `memory_` prefix and use snake_case, giving a predictable namespace. The verb ordering varies slightly (adjective+verb in batch_inspect, verb+preposition in find_by_intent, verb+noun elsewhere), but each name remains self-descriptive and readable.
Five tools is lean but each covers a distinct stage of the memory lifecycle (sync, search, bulk read, deep read, write). It stays well under the heavy-tool threshold and no tool feels redundant, though the surface is minimal for a full memory engine.
The read/create/sync path is covered, but there is no delete or invalidate operation for stale knowledge, no explicit update/amend for existing entries, and no listing/index tool to discover what folders are stored. Agents can work around some of this via search and re-enrich, but lifecycle coverage has notable holes.