Skip to main content
Glama

Save to memory

remember

Save important information to the user's Thread memory as a note, appending to an existing note when the title matches and optionally linking related notes.

Instructions

Save something important to the user's Thread memory. Adds to the note if the title already exists. related takes paths or titles of related notes to link to.

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

Input Schema

NameRequiredDescriptionDefault
tagsNo
titleYes
folderNoinbox
contentYes
relatedNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false; the description adds the non-obvious upsert behavior ("Adds to the note if the title already exists"), which explains why the call is non-idempotent and warns that content may be merged rather than replaced. It leaves open how title matching works (exact vs. fuzzy) and what folder does.

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?

Two short sentences, front-loaded with the core action and followed by the append rule and the `related` clarification. No filler, though the terse phrasing leaves gaps that could have been closed with a few more words.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. However, for a five-parameter write tool the description omits folder/tag semantics and the rules for title matching, leaving the agent to guess at organization and merge behavior.

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 0%, so the description carries the burden and it only partially does: it clarifies `related` (paths or titles of notes to link) and gives `title` a second role as the match key for appending. `folder` (default "inbox"), `tags`, and `content` receive no explanation, so three of five parameters remain opaque.

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 ("Save something important to the user's Thread memory") plus the key behavior that it appends when the title already exists. It does not name or contrast with siblings like link_notes or read_note, so an agent must infer that this is the write path for memory.

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?

"Save something important" implies when to use it but gives no concrete criterion for what counts as important, and no when-not guidance or named alternative (e.g. link_notes for relating existing notes). Usage is inferable rather than stated.

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