Skip to main content
Glama
Sign In
localmem

localmem

by sdc-ren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memory_add

Save durable facts, decisions, or lessons to persistent memory for recall across sessions. Add keywords to make memories searchable by lexical queries.

Instructions

Save a durable fact, decision, or lesson to the user's persistent memory. Call when you learn something worth remembering across sessions. A bug you fought: kind='lesson', one line: symptom — real cause — fix. Always pass keywords: synonyms, Vietnamese+English terms, error codes, symptoms — search is lexical.

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": "memory_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNonote
sourceNo
contentYes
keywordsNo
workspaceNo
supersedesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 burden. It discloses that memories are durable and persistent, and that search is lexical, which is useful. But it doesn't explain side effects, how supersedes works, or any authorization requirements, leaving notable gaps.

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?

Three sentences, front-loaded with the primary action, then usage guidance and parameter tips. Every sentence earns its place with no fluff.

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 memory-add tool with 6 optional params and an output schema, it covers the main use case, persistence, keywords, and content formatting. It leaves out semantics for source, workspace, and supersedes, but is otherwise quite complete for typical agent scenarios.

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 must compensate. It explains kind='lesson', content as one line, and keywords with specific examples. However, source, supersedes, and workspace are not touched, so three of six parameters remain undocumented.

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?

The description opens with 'Save a durable fact, decision, or lesson to the user's persistent memory', using a specific verb and resource. This clearly distinguishes it from the sibling tool memory_recall, which would retrieve memories.

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?

It explicitly states when to call: 'Call when you learn something worth remembering across sessions.' It also provides concrete formatting guidance for bug lessons. However, it doesn't mention exclusions or compare to memory_recall, so it falls short of a 5.

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