Skip to main content
Glama

remember

Save or update persistent notes for AI agents, using stable keys to keep one current value per fact and flag conflicts when an existing note disagrees.

Instructions

Save or update a note in the user's persistent memory. Re-using a title updates that note. Pass a stable key for a fact that should have one current value (e.g. 'storage-choice'); if a different active note already holds a different value for that key, the result warns you. If the project already uses a different-but-similar key, the result nudges you to reuse it. To replace an older note on purpose, add a line 'Supersedes: [[old-id]]' to the body.

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": {
      "title": "<title>",
      "body": "<body>"
    },
    "name": "remember"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoConflict-grouping key: one current value per key.
whyNoWhy this is being saved (recorded as provenance).
bodyYesMarkdown body. Link other notes with [[note-id]].
tagsNo
titleYesShort descriptive title; also determines the note id.
projectNoProject namespace, e.g. 'memex'. Defaults to 'general'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses that title reuse overwrites an existing note, that key collisions produce a warning in the result, and that similar-key detection produces a nudge. It still leaves open whether an update replaces the body/tags wholesale or merges them, which matters 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.

Conciseness4/5

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

Front-loaded with the core action, then progressively adds the update rule, the key/conflict rule, and the supersede mechanism in the order an agent would need them. Dense but every sentence carries operational information; no 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 6-parameter mutation tool with no annotations and no output schema, the description compensates well by describing the warning/nudge signals the caller should expect. Remaining gap is merge-vs-replace semantics on update, plus any per-namespace behavior for `project`.

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 already 83%, so the baseline is 3, but the description adds real meaning beyond it: `key` is explained functionally as a conflict group whose violation triggers a warning, and `body` is extended with the 'Supersedes: [[old-id]]' convention. `why`, `tags`, and `project` are left entirely to the schema.

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?

Opens with a specific verb+resource: 'Save or update a note in the user's persistent memory', and immediately clarifies the update trigger ('Re-using a title updates that note'). An agent can distinguish this write path from read-oriented siblings like read_note and recall without opening the schema.

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?

Gives a usable decision structure: reuse a title to update, pass a stable `key` for single-valued facts, and add a 'Supersedes: [[old-id]]' line for deliberate replacement. It never names an alternative tool or states when not to use this one, so the routing guidance is implicit rather than explicit.

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