Skip to main content
Glama

Memlord

by com.memlord
OverviewDiscussionsAdmin

store_memory

Idempotent

Save a new memory. Idempotent: returns existing if content already stored.

name: human-readable name, unique within the workspace. workspace: name of the workspace to store into. Omit to store as a personal memory. force: skip near-duplicate check and store unconditionally. expires_at: optional UTC expiry; after it passes the memory is hidden from reads.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
tagsNo
forceNoSkip near-duplicate check and store unconditionally.
contentYes
metadataNo
workspaceNoName of the workspace to store into (must be a member). Omit or pass None to store as a personal memory.
expires_atNoUTC timestamp after which the memory is hidden from search and list results (still retrievable by exact name via get_memory). Expired memories are purged via the profile 'clean up expired' button. None = never expires.
memory_typeYesfact: established fact about user, project, or system. preference: user's likes, dislikes, habits. instruction: persistent rule Claude must follow. feedback: evaluation of Claude's output. decision: a choice made with reasoning ('chose X over Y because Z'). insight: consolidated conclusion distilled from several existing memories.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
createdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / expires_at
      Added value: +{
+  "anyOf": [
+    {
+      "format": "date-time",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "UTC timestamp after which the memory is hidden from search and list results (still retrievable by exact name via get_memory). Expired memories are purged via the profile 'clean up expired' button. None = never expires."
+}
    • addedInput schema / properties / force / description
      Added value: +"Skip near-duplicate check and store unconditionally."
    • changedInput schema / properties / memory_type / description
      Previous value: -"fact: established fact about user, project, or system.\npreference: user's likes, dislikes, habits.\ninstruction: persistent rule Claude must follow.\nfeedback: evaluation of Claude's output.\ndecision: a choice made with reasoning ('chose X over Y because Z')."New value: +"fact: established fact about user, project, or system.\npreference: user's likes, dislikes, habits.\ninstruction: persistent rule Claude must follow.\nfeedback: evaluation of Claude's output.\ndecision: a choice made with reasoning ('chose X over Y because Z').\ninsight: consolidated conclusion distilled from several existing memories."
    • changedInput schema / properties / memory_type / enum
      Previous value: -[
-  "fact",
-  "preference",
-  "instruction",
-  "feedback",
-  "decision"
-]New value: +[
+  "fact",
+  "preference",
+  "instruction",
+  "feedback",
+  "decision",
+  "insight"
+]
    • addedInput schema / properties / name
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / workspace / description
      Added value: +"Name of the workspace to store into (must be a member). Omit or pass None to store as a personal memory."
    • changedInput schema / required
      Previous value: -[
-  "content",
-  "memory_type"
-]New value: +[
+  "content",
+  "memory_type",
+  "name"
+]
    • removedOutput schema / properties / id
      Removed value: -{
-  "title": "Id",
-  "type": "integer"
-}
    • addedOutput schema / properties / name
      Added value: +{
+  "title": "Name",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "id",
-  "created"
-]New value: +[
+  "name",
+  "created"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / memory_type / description
      Added value: +"fact: established fact about user, project, or system.\npreference: user's likes, dislikes, habits.\ninstruction: persistent rule Claude must follow.\nfeedback: evaluation of Claude's output.\ndecision: a choice made with reasoning ('chose X over Y because Z')."
    • changedInput schema / properties / memory_type / enum
      Previous value: -[
-  "fact",
-  "preference",
-  "instruction",
-  "feedback"
-]New value: +[
+  "fact",
+  "preference",
+  "instruction",
+  "feedback",
+  "decision"
+]
  3. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the baseline is set. The description adds real value beyond them: a near-duplicate check runs by default and is skipped only with force, expired memories remain retrievable by exact name via get_memory, and purging happens through a profile clean-up action. It does not describe return shape, but that is defensible given the idempotency note.

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?

Front-loaded one-line purpose followed by compact per-parameter bullets; nothing is wasted. The only blemish is that the workspace and force blurbs are near-verbatim duplicates of the schema descriptions, which is mild redundancy rather than bloat.

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?

An output schema exists, so return values need no explanation, and the description covers creation semantics, dedup behavior, workspace scoping, and expiry. It is adequate for an 8-parameter write tool, though it could say more about what content or memory_type should contain and where the sibling update_memory takes over.

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?

With only 50% schema description coverage across 8 parameters, the description must compensate, and it does for the four most ambiguous ones: name uniqueness, workspace membership vs personal-memory default, force semantics, and the expiry lifecycle. content, tags, and metadata are left unexplained, but those are largely self-evident and memory_type carries a detailed enum in the schema.

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?

The opening sentence gives a specific verb+resource ("Save a new memory") and the word "new" implicitly distinguishes it from the update_memory sibling. However, it never explicitly names or contrasts with update_memory, recall_memory, or retrieve_memory, so an agent must infer the boundary itself.

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

Usage Guidelines2/5

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

The description states the tool is idempotent and returns existing content, which implies the caller need not pre-check for duplicates, but it never states when to use this over update_memory for existing memories or why not to use it for retrieval. No prerequisites, exclusions, or alternative routing are given despite ten siblings covering overlapping memory operations.

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

All Memlord toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources