Skip to main content
Glama
Sign In
frugal-memory

frugal-memory

by komakeule57-maker
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

recall

Search persistent AI memory by keyword to find prior notes and decisions before checking files or the web. Returns ranked previews you can expand.

Instructions

Searches memory by words, best matches first.

Use it first, before searching files or the web for something noted before. It matches words, not meaning: inflected forms count ("configured" -> "configuring"), synonyms don't - if nothing fits, retry in the other language your notes may use. No search terms? Browse with topics.

Returns a preview per hit (id, kind, date, title line). Read the ones you need with show("376,481"), or set full=True for a narrow question.

Args: query: Search term(s), FTS5 syntax allowed (e.g. "sqlite AND fts5", "proj*"). limit: Maximum number of hits (default 8). kind: Restrict to kinds of knowledge, e.g. "pitfall,decision". Possible: interface, pitfall, decision, measurement, workflow, history, unsorted, all. Default: everything except history - otherwise the chronicle drowns out every search for a detail. tag: Restrict to a project, e.g. "spaceship". Several tags separated by comma or space are OR-combined. Sub-tags are included: "lighthouse" also matches "lighthouse-project", but "mcp-memory-server" does not match "mcp-memory". topics() lists which tags exist. full: Full text instead of preview (default: no), capped like show. include_superseded: Also show superseded entries (default: no).

Input Schema

NameRequiredDescriptionDefault
tagNo
fullNo
kindNo
limitNo
queryYes
include_supersededNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.3.0
    • removedInput schema / properties / art
      Removed value: -{
-  "default": "",
-  "type": "string"
-}
    • addedInput schema / properties / full
      Added value: +{
+  "default": false,
+  "type": "boolean"
+}
    • addedInput schema / properties / include_superseded
      Added value: +{
+  "default": false,
+  "type": "boolean"
+}
    • addedInput schema / properties / kind
      Added value: +{
+  "default": "",
+  "type": "string"
+}
    • removedInput schema / properties / marke
      Removed value: -{
-  "default": "",
-  "type": "string"
-}
    • removedInput schema / properties / mit_veraltet
      Removed value: -{
-  "default": false,
-  "type": "boolean"
-}
    • addedInput schema / properties / tag
      Added value: +{
+  "default": "",
+  "type": "string"
+}
    • removedInput schema / properties / voll
      Removed value: -{
-  "default": false,
-  "type": "boolean"
-}
  2. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it explains word-based matching, inflection handling, lack of synonym matching, default exclusion of history, preview return shape, and superseded-entry behavior. These are material behavioral traits beyond the schema.

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?

The description is front-loaded with purpose and search semantics, then supplies argument details needed because schema coverage is zero. The structure is dense but each sentence contributes relevant selection or invocation information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given six parameters, no annotations, and an output schema, the description covers both behavior and argument semantics thoroughly. The output schema can carry return details, but the included preview explanation further helps an agent understand what recall returns.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate, and it does: query syntax, limit default, kind values and default exclusion, tag OR-combination and sub-tag matching, full behavior, and include_superseded are all explained. This adds substantial meaning beyond bare parameter names.

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 states a specific action and resource: searching memory by words, with best matches first. It distinguishes itself from file/web search and explicitly routes browsing to topics and reading hits to show, so sibling selection is clear.

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?

It gives explicit when-to-use guidance (use first, before files or web), when to switch (no search terms → topics, read hits → show), and how to handle failed matches (retry in the other language). Alternatives are named, not implied.

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