Skip to main content
Glama
Sign In
chat-memory

chat-memory

by mav-rix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

update_memory

Edit an existing memory and keep prior text as a version; use pinned=true to add it to every session's profile.

Instructions

Change an existing memory. The previous text is kept as a version. pinned=true puts it in every session's profile.

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": {
      "memory_id": "<memory_id>"
    },
    "name": "update_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
tagsNo
titleNo
pinnedNo
contentNo
memory_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full load, and it does disclose two real behaviors: prior text is retained as a version, and pinned memories surface in every session profile. It omits the consequences of a bad memory_id, whether omitted or null fields are left untouched versus cleared, and any permission or auth requirements — meaningful gaps for a mutation tool.

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

Conciseness5/5

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

Three short sentences, zero filler, with the core action stated first and the behavioral notes layered after it. Nothing in the text is redundant with the name or title.

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

Completeness2/5

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

An output schema exists, so return values needn't be described, but six parameters at 0% schema coverage and no annotations leave the definition under-specified for a mutation tool. An agent still cannot tell whether passing null clears a field or preserves it, or what happens when memory_id does not resolve.

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 0% across six parameters, so the bar is high; the description only explains pinned, while content, title, kind, tags, and memory_id carry no meaning beyond their names. It earns partial credit for clarifying the non-obvious effect of pinned, but the crucial ambiguity of null-defaulted fields (no change vs. clear) is left entirely unaddressed.

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?

'Change an existing memory' gives a specific verb and resource, and the versioning sentence distinguishes it from a create-style tool like remember. It does not name the near-neighbor supersede, so an agent must infer which mutation tool to pick when an existing memory should be replaced rather than edited.

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?

No explicit when-to-use guidance: the description never says when to edit in place versus calling remember, forget, or supersede. The only actionable conditional is 'pinned=true puts it in every session's profile', which is field semantics rather than tool selection guidance.

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

Deploy Server

Other Tools