Skip to main content
Glama

Save memory

save_memory
Destructive

Save an important fact, decision, or preference to long-term memory for future conversations. ALWAYS use this when the user shares personal details like their name, role, or team. Also use when the user explicitly asks to remember something, when a significant decision is made (e.g., architecture choice, naming convention, preferred namespace), when a non-obvious issue is resolved and the root cause should be remembered, or when cluster-specific topology is discovered (e.g., installed operators, resource patterns). Keep entries concise and factual. Do not save generic Kubernetes knowledge. Set cluster_specific=false for personal or organization-wide facts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "content": "<content>"
    },
    "name": "save_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesThe fact, decision, or insight to save. Be concise and specific.
cluster_specificNoWhether this memory is specific to the current cluster (true) or applies globally to the user (false). Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations declare destructiveHint=true and idempotentHint=false, but the description never explains what that means in practice: whether saving a similar fact overwrites or duplicates an existing memory, and whether the write is reversible. It does add behavioral guidance absent from annotations ('Keep entries concise and factual', don't store generic knowledge), which earns credit, but the destructive/non-idempotent profile is left unexplained.

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?

Front-loaded with the core action, then trigger conditions, then the exclusion and parameter rule. The middle sentence is a long enumeration but each clause carries distinct routing information; minor tightening possible but nothing is filler.

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?

For a two-parameter write tool with no output schema, the definition covers what to save, when to save it, what not to save, and how to set the scoping flag. The only meaningful gap is overwrite/duplication behavior implied by destructiveHint=true and idempotentHint=false.

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

Parameters4/5

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

Schema coverage is 100%, so both parameters are already documented. The description nonetheless adds real meaning by giving a decision rule for cluster_specific ('Set cluster_specific=false for personal or organization-wide facts'), which is more actionable than the schema's phrasing, and reinforces content conciseness.

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

Purpose5/5

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

States a specific verb and resource ('Save an important fact, decision, or preference to long-term memory') plus the purpose ('for future conversations'). No sibling tool in the provided list performs memory persistence, so the tool is unambiguous on its own terms.

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

Usage Guidelines5/5

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

Enumerates concrete trigger conditions: user shares personal details, explicit request to remember, significant decision, non-obvious root cause resolved, cluster topology discovered. It also states a negative case ('Do not save generic Kubernetes knowledge'), which is the exclusion guidance most definitions omit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.