Skip to main content
Glama

memory_save

Save a memory to the local shared store for cross-agent reuse across sessions. Returns a write receipt covering what was stored, its source, and how to undo it.

Instructions

保存一条记忆到本地共享记忆库(跨 Agent 可见)。返回写回回执:写了哪条 / 归到哪 / 出自哪 / 怎么撤 —— 请把回执转述给用户,没有任何东西会静默进入长期记忆

Input Schema

NameRequiredDescriptionDefault
tagsNo逗号分隔标签
turnNo可选:出自该会话的第几轮
typeNo记忆类型
agentNo写入方 Agent 名
branchNo可选:这条结论属于哪个 Git 分支。**不传时会自动读当前目录的 git 分支**(读不到就留空);传空串表示明确与本分支无关。同分支的记忆在 memory_context 里排前面。不能带换行/控制字符(会被当成新章节注入给别的 Agent)
contentYes记忆内容(中文友好)
projectNo所属项目名
importanceNo重要度1-4
session_idNo可选:这条结论出自哪段已归档会话(面板「会话」页的编号)。填了就能在面板里溯源回原话
skip_checkNo可选:默认 true 走排除清单(拦掉工具输出残骸/纯符号/表格碎片等无信息量内容)。确实要原样存就传 false

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

无 annotations 时描述需承担全部行为披露责任,而它明确说明了返回“写回回执”的内容(写了哪条/归到哪/出自哪/怎么撤)以及“没有任何东西会静默进入长期记忆”的写入语义,并附带让 Agent 把回执转述给用户的行为要求。未提及权限、限额等,但核心行为(可撤销、非静默写入)已披露。

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

两句、前置了作用域与回执要点,信息密度高。回执四个要点用斜杠紧凑并列,无冗余铺垫,但整体略显压缩、可读性一般。

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

对一个 10 参数、无 output schema 的写入工具,描述通过说明返回回执的内容弥补了缺少输出 schema 的空白,且点明可撤销性。但缺少与兄弟工具的分工说明,Agent 仍无法完全判断调用边界。

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema 描述覆盖率 100%,10 个参数(含 branch 的自动读 git 分支、skip_check 默认 true 的排除逻辑、session_id 溯源等)已在 schema 中充分说明。描述未对参数做任何补充,按规则在高覆盖率下取基线 3。

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

明确的动词+资源:“保存一条记忆到本地共享记忆库”,并给出了区别于 session_save 等兄弟工具的关键作用域特征——“跨 Agent 可见”。但并未点名任何兄弟工具,无法帮助 Agent 在 memory_save 与 session_save 之间直接做区分。

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

没有给出何时使用本工具、何时应改用兄弟工具的显式说明。仅在末尾暗示写入是持久化/长期记忆,需要 Agent 自行推断它与 session_save、memory_handoff、memory_pin 的分工。

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.