Skip to main content
Glama

update_memory

Update an existing memory in the active ContextDrop project when new durable project knowledge materially changes or improves that memory. Use this proactively when appropriate; do not require the user to explicitly say "update this". Search for the existing memory first when the memory_id is not already known. Do not overwrite memories merely because information is similar, uncertain, speculative, temporary, or unrelated. Never store secrets or credentials.

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
titleNo
contentNo
categoryNo
memory_idYes
memory_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / category / enum
      Added value: +[
      +  "Technical",
      +  "Architecture",
      +  "Product",
      +  "Security",
      +  "Business",
      +  "Customer",
      +  "Content",
      +  "Operations",
      +  "Personal"
      +]
    • removedInput schema / properties / category / maxLength
      Removed value: -100
    • removedInput schema / properties / category / minLength
      Removed value: -1
    • addedInput schema / properties / memory_type
      Added value: +{
      +  "enum": [
      +    "Fact",
      +    "Definition",
      +    "Decision",
      +    "Constraint",
      +    "Requirement",
      +    "Convention",
      +    "Preference",
      +    "Workflow",
      +    "Reference"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.6/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 behavioral burden; it does add real policy context such as the no-overwrite rule and the secrets prohibition. However, it never discloses core mutation semantics: whether omitted fields (title, content, category, memory_type) are preserved or cleared, whether prior content is versioned or recoverable, or what the call returns.

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?

The purpose is front-loaded in the first sentence, followed by usage rules in a compact, scannable sequence with no filler. It reads as a short rule list rather than prose, but every sentence adds a distinct constraint.

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 5-parameter mutation tool with no annotations and no output schema, the description covers policy well but leaves the mechanical contract underspecified — partial versus full update behavior and return values are unaddressed. Adequate to select the tool, insufficient to call it confidently.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, yet it only addresses memory_id (search for it first). The meaning of content, title, category, and memory_type — particularly whether content replaces the entire body or merges — is left entirely to the bare schema and enum values.

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 opens with a specific verb and resource ('Update an existing memory') and scopes it to 'the active ContextDrop project'. The word 'existing' implicitly separates it from save_memory, but no sibling is named explicitly, so an agent must infer the boundary rather than being routed.

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?

It states the trigger condition (durable project knowledge materially changes or improves the memory), grants proactive use without explicit user instruction, prescribes searching first when memory_id is unknown, and lists explicit exclusions: similar, uncertain, speculative, temporary, or unrelated information. This is a complete when/when-not set with a concrete prerequisite.

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.

Resources