No user-submitted related servers found.
Scored across 14 tools
The set splits cleanly into a project cluster, a memory cluster, and daily_brief, and within each cluster verbs distinguish intent well (recall vs history vs conflicts, remember vs correct vs forget). The weak spot is project_add vs project_update and project_close: despite the 'project_' prefix, add/close operate on items (blockers, next steps, follow-ups) while update operates on projects, so an agent can misread which resource is being mutated. Descriptions do resolve the ambiguity once read, so no more than a modest penalty.
Almost every tool follows a consistent domain_verb snake_case pattern (project_*, memory_*), and the verb positions are predictable across both clusters. The single deviation is daily_brief, which has no domain prefix and leads with a noun, breaking the otherwise uniform scheme.
Fourteen tools is comfortably within the well-scoped range, and each one maps to a distinct lifecycle operation (add/close/decide/resume/list/update for projects; remember/recall/correct/forget/history/conflicts/stats for memory) plus one aggregate briefing. No filler or near-duplicate tools are present.
Memory coverage is close to a full lifecycle (create, search, supersede, delete, history, conflict detection), and projects support creation, item intake, resolution, decisions and resumption briefing. Gaps remain minor but real: there is no way to enumerate all memories without a search query (no memory_list), no way to edit or delete an individual project item short of closing it, and no way to remove a project entirely.