| name | memory-store-basics |
| description | Use when starting Memory Store-backed work, orienting an agent to company memory, using briefs or living docs, deciding whether to record a learning, or deciding whether a new brief is warranted. Requires Memory Store MCP. |
Memory Store Basics
Use Memory Store as the context substrate for agent-native work. The core loop is:
checkin -> list/select briefs -> recall evidence -> act -> record confirmed learning -> update/propose brief changes only when operating truth changed
Required MCP Operations
Memory Store MCP provides:
checkin - start or resume the focused thread.recall - retrieve evidence, decisions, prior context, and source memories.list-briefs - see maintained synthesis documents available to the agent.record - store confirmed learnings, rules, decisions, corrections, and outcomes.report-issue - report broken Memory Store behavior when the user asks or the tool behaves unexpectedly.
Tool names may be namespaced by the host. Use the operation names, not exact host-specific names, in user-facing explanations.
Some hosts also expose lower-level brief tools. Treat them as edit controls over the brief layer, not as substitutes for record:
get_brief - read one selected brief when its summary is not enough.suggest_brief_change - attach a proposed delta without claiming the brief changed.teach_brief - save an explicit correction on a brief and teach it back to memory.save_brief or save_brief_section - create or edit a canonical brief only after approval or when the user directly asked for the edit.
