Skip to main content
Glama
mergestorm-mcp

mergestorm-mcp

Official

Update memory

update_memory
DestructiveIdempotent

Correct an inaccurate or outdated memory by ID with new text and an optional kind, keeping stored project knowledge current.

Instructions

Correct a memory that is wrong or out of date: its id from list_memories or search_memory, the new text, and optionally a new kind.

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

Input Schema

NameRequiredDescriptionDefault
idYes
kindNo
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.31

TDQS

A3.8/5.0
Behavior3/5

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

The description adds the useful fact that the id must be obtained from list_memories or search_memory first. However, with destructiveHint=true and readOnlyHint=false, the description should say that the existing text is overwritten and whether the old value is recoverable; it also doesn't say whether omitting kind preserves the current kind. It does not contradict the annotations.

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?

A single compact sentence with no filler, front-loading the purpose before listing the inputs. Nothing is repeated from the schema or title.

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

Completeness3/5

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

For a destructive, idempotent mutation with no output schema, the definition covers purpose and params adequately but omits consequences: what happens to the old text, whether the update is reversible, and any permission or rate-limit considerations. Those gaps matter given destructiveHint=true.

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 description coverage is 0%, so the description carries the full load, and it does describe all three params: id with its provenance, the new text, and the optional new kind. It leaves the kind enum values (rule/style/preference/fact/project) to speak for themselves and gives no constraints such as the 500-character text limit.

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?

The description gives a specific verb ('Correct') and resource ('a memory'), plus the condition that the memory is 'wrong or out of date'. It also points at list_memories/search_memory as the source of the id, which helps separate this from creation tools, though it never explicitly contrasts with forget_memory or remember.

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

Usage Guidelines4/5

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

It states a clear trigger for use ('wrong or out of date' memories) and clarifies that kind is optional while id and text are the core inputs. It stops short of naming the alternatives for removal (forget_memory) or addition (remember), and does not say when a correction should instead be a delete-and-recreate.

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