Memlord

Overview Schema Source Related Servers Discussions Admin

recall_memory

Read-only

Search memories using time expressions and semantic queries. Filter by workspace or memory type to retrieve names and metadata.

Instructions

Search memories by time expression + semantics. Returns names + metadata only.

Examples: "last week", "yesterday", "about Python last month". Use get_memory(name=...) to fetch full content of a specific result. Pass workspace= to search only within a specific workspace.

Input Schema

TableJSON Schema

Name	Required	Description
`query`	Yes	Query string
`n_results`	No
`workspace`	No
`memory_type`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedMay 1, 2026
Removedv0.2.8Apr 11, 2026

Changed5 schema fields changedv0.2.7Apr 6, 2026

addedOutput schema / properties / items

Added value: +{
+  "items": {
+    "properties": {
+      "content": {
+        "title": "Content",
+        "type": "string"
+      },
+      "created_at": {
+        "format": "date-time",
+        "title": "Created At",
+        "type": "string"
+      },
+      "id": {
+        "title": "Id",
+        "type": "integer"
+      },
+      "memory_type": {
+        "anyOf": [
+          {
+            "enum": [
+              "fact",
+              "preference",
+              "instruction",
+              "feedback"
+            ],
+            "title": "MemoryType",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "tags": {
+        "items": {
+          "type": "string"
+        },
+        "title": "Tags",
+        "type": "array",
+        "uniqueItems": true
+      },
+      "workspace_id": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Workspace Id"
+      }
+    },
+    "required": [
+      "id",
+      "content",
+      "memory_type",
+      "tags",
+      "created_at"
+    ],
+    "title": "RecallResult",
+    "type": "object"
+  },
+  "title": "Items",
+  "type": "array"
+}

removedOutput schema / properties / result

Removed value: -{
-  "items": {
-    "properties": {
-      "content": {
-        "type": "string"
-      },
-      "created_at": {
-        "format": "date-time",
-        "type": "string"
-      },
-      "id": {
-        "type": "integer"
-      },
-      "memory_type": {
-        "anyOf": [
-          {
-            "enum": [
-              "fact",
-              "preference",
-              "instruction",
-              "feedback"
-            ],
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "tags": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array",
-        "uniqueItems": true
-      },
-      "workspace_id": {
-        "anyOf": [
-          {
-            "type": "integer"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null
-      }
-    },
-    "required": [
-      "id",
-      "content",
-      "memory_type",
-      "tags",
-      "created_at"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```
addedOutput schema / title
```
Added value: +"RecallPage"
```
removedOutput schema / x-fastmcp-wrap-result
```
Removed value: -true
```

First observedv0.2.4Apr 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that it returns only names and metadata, and that search combines time and semantic expressions. No contradictions with annotations.

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 plus examples, front-loaded with purpose. Every sentence adds value without redundancy. Efficiently structured.

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 main usage, examples, workflow (use get_memory for full content), and workspace filtering. Missing details on n_results and memory_type parameters, but output schema exists to document return values, balancing completeness.

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?

The description explains the 'query' parameter with examples and mentions the 'workspace' parameter. However, it does not cover 'n_results' or 'memory_type', and schema description coverage is only 25%, so the description provides partial but not complete compensation.

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 'Search memories by time expression + semantics. Returns names + metadata only.' It identifies the tool's primary function and its output scope, distinguishing it from get_memory which fetches full content.

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 examples of queries and directs to use get_memory for full content retrieval. Also explains how to limit search to a workspace. However, it does not differentiate from sibling tools like retrieve_memory or search_by_tag.

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

Deploy Server