Skip to main content
Glama
thuupx

memory-mcp-lite

by thuupx

Store a fact / command / gotcha

remember_fact

Persist a concise atomic memory: fact, command, gotcha, link, or convention for reuse.

Instructions

Persist a concise atomic memory: fact, command, gotcha, link, or convention. USE WHEN: the user gives concrete reusable info (a command, env detail, integration note, rule). DO NOT USE WHEN: the info is a major decision (use remember_decision) or a summary (use upsert_*_summary). FACT TYPES: fact | command | gotcha | link | convention | decision (prefer remember_decision for 'decision'). RETURNS: { project_id, memory_id }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesShort title for the fact (max 200 chars)
sourceNoOptional source pointer (file path, PR url, doc link)
contentNoOptional extended detail or example usage
summaryYesConcise fact body (max 500 chars)
git_rootNoAbsolute path to the git repository root
fact_typeNoAtomic memory type: fact | command | gotcha | link | convention | decision. Prefer remember_decision for 'decision'.fact
importanceNo0.0-1.0, defaults to the type-specific default in MemoryPolicy
project_idNoExplicit project id
remote_urlNoGit remote URL
workspace_pathNoAbsolute path to the workspace root

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
memory_idYes
project_idYes
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false. The description adds that it returns {project_id, memory_id} and provides fact type guidance. No contradictions, but could mention idempotency (idempotentHint=false).

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?

Every sentence adds value: purpose, usage, types, return. Front-loaded, no fluff, well-structured with section headings.

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?

With 10 parameters, 100% schema coverage, and output schema, the description covers purpose, usage, and return. Minor gap: no mention of overwrite or duplicate behavior, but annotations and schema handle most.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline 3. Description adds context for fact_type enum and its preferred usage, improving parameter understanding beyond schema.

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 clearly states the verb 'persist' and resource 'atomic memory', and distinguishes from sibling tools like remember_decision and upsert summaries by specifying concrete, reusable info types.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit USE WHEN and DO NOT USE WHEN sections provide clear context and name alternatives (remember_decision for decisions, upsert summaries for summaries).

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/thuupx/memory-mcp-lite'

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