Skip to main content
Glama
Sign In
Unified Memory MCP

Unified Memory MCP

by piligrim-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memory_save

Save facts, preferences, decisions, and context to a shared local store that Codex and Claude can read, with auto-chunking and embeddings for semantic recall.

Instructions

Save a memory (fact, preference, decision, context) to the shared local store that both Codex and Claude read. Auto-chunked and embedded for semantic recall. Use for durable info worth recalling.

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_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoOptional tags.
scopeNoBucket, e.g. 'global' or a project. Default 'global'.
sourceNoWho is writing, e.g. 'claude' or 'codex'.
contentYesThe fact to remember.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.5.1

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 carries the full burden. It does disclose real behavior beyond the name – auto-chunking, embedding for semantic recall, and the shared cross-agent store – which is genuinely useful. But it says nothing about deduplication, overwrite semantics, permissions, or what identifier is returned for later update/delete by the sibling tools.

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 short sentences, front-loaded with the action and destination, then the mechanism, then the usage cue. No filler or redundancy.

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 no-annotation, no-output-schema mutation tool it covers the essentials (what it stores, where, how it is indexed). It omits the practical follow-up information an agent needs in a 15-tool memory suite – the returned handle and whether repeated saves overwrite or duplicate.

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 schema already documents all four parameters, including defaults for scope and examples for source. The description adds no syntax, format, or constraint detail beyond what the schema provides, making the baseline 3 appropriate.

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 (Save) and resource (a memory) and enumerates the content categories it accepts, plus the destination ('shared local store that both Codex and Claude read'). It does not differentiate itself from siblings like memory_update or handoff_save, which could be confused for similar write operations.

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?

'Use for durable info worth recalling' gives a positive usage condition but is fuzzy and names no alternatives or exclusions. An agent still has to infer why it would pick memory_save over handoff_save or memory_update.

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