Skip to main content
Glama
Sign In
ContextOS

ContextOS

by aftabkh4n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

remember

Save workspace memories to local SQLite so later AI coding sessions can recall decisions, notes, and gotchas.

Instructions

Saves a memory for this workspace so later sessions can recall it. Stored verbatim in a local SQLite file. Memories not recalled for 90 days (default) are archived. Returns JSON {id, message}.

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

Input Schema

NameRequiredDescriptionDefault
tagsNoComma-separated tags, for example auth,api
typeNonote (default), decision, gotcha, todo, or skillnote
contentYesThe text to store, kept verbatim
importanceNo0.0 to 1.0 (default 0.5). Higher ranks earlier in recall.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.5
    • changedInput schema / properties / content / description
      Previous value: -"Content"New value: +"The text to store, kept verbatim"
    • changedInput schema / properties / importance / description
      Previous value: -"0.0-1.0"New value: +"0.0 to 1.0 (default 0.5). Higher ranks earlier in recall."
    • changedInput schema / properties / tags / description
      Previous value: -"Comma-separated tags"New value: +"Comma-separated tags, for example auth,api"
    • changedInput schema / properties / type / description
      Previous value: -"note, decision, gotcha, todo, skill"New value: +"note (default), decision, gotcha, todo, or skill"
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and does real work here: it names the storage medium (local SQLite file), states content is stored verbatim, and discloses the archival lifecycle (memories not recalled for 90 days, default, get archived). It omits reversibility, duplicate handling, and any permission requirements, which keeps it below 5.

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?

Four short, front-loaded sentences each carrying distinct information: purpose, storage medium, retention lifecycle, and return shape. Nothing is wasted, though the return-shape sentence is close to restating structured information a moment later.

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?

No output schema exists, so specifying the return as JSON {id, message} is genuinely useful. Combined with storage location, verbatim semantics, and retention policy, this covers what an agent needs to call a simple four-parameter write tool correctly.

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 all four parameters are already documented, including the type taxonomy and the importance range. The description adds essentially nothing new on parameters, only repeating 'kept verbatim' which the schema already states, so baseline 3 applies.

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?

Specific verb and resource: 'Saves a memory for this workspace so later sessions can recall it.' That makes it distinguishable from the read-side sibling recall and the specialized remember_skill without opening either schema.

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 rather than stated: 'so later sessions can recall it' positions this as the write half of a remember/recall pair, and a sibling named recall exists. But there is no explicit when-to-use-this-vs-alternative sentence and no exclusion rule telling the agent when to prefer remember_skill.

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