Skip to main content
Glama
gabrimatic

mcp-prose-memory

by gabrimatic

memory

Store and manage persistent facts across sessions. Add, view, update, or remove structured memories organized by sections like work, personal, and preferences.

Instructions

Manage persistent memory across sessions.

Commands:

  • view: Show all memories (optionally filter by section)

  • add: Add a new fact to a section

  • upsert: Add or replace a structured fact by key

  • remove: Remove a fact by section and line number

  • replace: Update a fact by section and line number

Sections: work, personal, top_of_mind, history, instructions, user_profile, user_preferences, eyra_project, devices_environment, workflows, writing_style, long_term_tasks, do_not_forget

Examples:

  • {"command": "view"}

  • {"command": "view", "section": "work"}

  • {"command": "add", "section": "personal", "fact": "Lives in Berlin"}

  • {"command": "upsert", "section": "user_preferences", "key": "answer_style", "value": "Prefers concise answers"}

  • {"command": "remove", "section": "work", "line": 3}

  • {"command": "replace", "section": "top_of_mind", "line": 1, "fact": "Working on new project"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYesOperation to perform
sectionNoTarget section (required for add/remove/replace, optional for view)
sectionsNoOptional section allowlist for compact view/context output
factNoFor add/replace: the fact to store (max 300 chars)
keyNoStable compact key for structured facts
valueNoCompact value for structured facts
sourceNoShort source label for structured facts
confidenceNoConfidence label for structured facts
lineNoFor remove/replace: line number within section (1-indexed)
formatNoOutput format for view
maxCharsNoMaximum characters for view output
Behavior3/5

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

No annotations provided, so the description must carry the burden of behavioral disclosure. It describes operations and constraints (e.g., max lengths) but does not mention side effects, save guarantees, or performance impacts.

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?

Well-structured with sections for commands, sections, and examples. Slightly verbose due to listing all sections, but the structure aids readability.

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?

Covers all 11 parameters with examples and command details. No output schema is provided, but the description sufficiently explains what each command does. However, it does not describe return values or error handling.

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?

Input schema has 100% description coverage, so baseline is 3. The description groups parameters by command and provides examples, which adds some value but does not significantly extend beyond the schema's parameter descriptions.

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?

Clearly states it manages persistent memory across sessions. Lists specific commands (view, add, upsert, remove, replace) and sections, distinguishing it from the sibling tool 'memory_context' which likely provides context retrieval.

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?

Provides explicit commands and sections, but does not contrast with the sibling 'memory_context' to clarify when to use this tool vs. the other. However, the examples and command list make usage clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gabrimatic/mcp-prose-memory'

If you have feedback or need assistance with the MCP directory API, please join our Discord server