Skip to main content
Glama
Kaede Recall MCP

Kaede Recall MCP

memory-update

Edit a stored long-term memory in place, including text, summary, tags, or entities, and re-embed it automatically when the trigger or body changes.

Instructions

Edit a stored memory in place: text, summary, tags or entities. Re-embeds when the trigger or the body changes.

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": {
      "point_id": "<point_id>"
    },
    "name": "memory-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoComma separated tags. Replaces the current tags.
textNoNew body. Recomputes the hash, re-extracts entities and re-embeds summary + first 1200 chars.
summaryNoNew one-line trigger. Re-embeds the memory.
entitiesNoComma separated aliases. Replaces the current entities.
point_idYesThe id of the memory to edit, as returned by memory-recall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the full burden, and it does disclose a real side effect: re-embedding when the trigger or body changes. However, key behaviors remain undisclosed for a mutation tool — whether omitted (null-defaulted) fields are left untouched or cleared, what happens for a non-existent point_id, and whether partial edits invalidate derived data.

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?

Two sentences, zero filler, with the operation and the field list front-loaded and the side effect trailing. Nothing is repeated or padding.

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 definition covers what the tool does and its main side effect but leaves callers guessing about the response, failure modes, and the semantics of omitted fields. Adequate but with clear gaps.

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 description coverage is 100%, so the baseline is 3; the per-parameter descriptions already explain hashing, entity re-extraction and re-embedding. The description reinforces the field set and the 'in place' partial-update framing but adds no syntax, format, or null-handling detail beyond the schema.

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?

States a specific verb and resource ('Edit a stored memory in place') and enumerates the editable fields (text, summary, tags, entities), which is enough to separate it from the write/delete siblings. It does not name those siblings explicitly, so the differentiation is inferred from 'in place' rather than stated.

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

Usage Guidelines3/5

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

Usage is implied: 'Edit a stored memory in place' signals mutation of an existing record rather than creation, and 'as returned by memory-recall' hints at the prerequisite lookup. There is no explicit when-to-use vs memory-write guidance, no statement that only supplied fields change, and no error/prerequisite conditions.

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