No user-submitted related servers found.
Scored across 39 tools
Multiple overlapping clusters create real selection ambiguity: six retrieval tools (plur_recall, plur_recall_hybrid, plur_similarity_search, plur_inject, plur_inject_hybrid, plur_timeline) and five creation paths (plur_learn, plur_learn_batch, plur_ingest, plur_capture, plur_episode_to_engram) have fuzzy boundaries. An agent will struggle to choose between plur_recall_hybrid vs plur_similarity_search, or plur_pin vs plur_promote, since both pairs control injection visibility.
The plur_ prefix is applied uniformly and resource families like packs_* and stores_* follow tidy noun-verb patterns, but the set mixes verb-led names (plur_learn, plur_recall, plur_forget) with bare nouns (plur_timeline, plur_status, plur_history, plur_profile, plur_tensions) and odd entries like plur_doctor and plur_similarity_search. Readable, but not a single predictable convention.
At 39 tools, this is well into the overgrown range. While the domain is genuinely broad, several tools are near-duplicates (recall/recall_hybrid, inject/inject_hybrid, learn/learn_batch), and subdomains like tensions and meta-engrams add complexity that could be consolidated. The cognitive load on an agent selecting from 39 options is high.
The surface covers the full engram lifecycle — create (learn, learn_batch, ingest, capture), query (recall, timeline, history), update (feedback, pin, promote), and retire (forget) — plus packs, scopes, sync, meta-engrams, and diagnostics. Minor gaps: there is no direct get-engram-by-ID tool, and content edits happen implicitly through the learn dedup pipeline rather than an explicit update tool.
