Skip to main content
Glama
udjin-labs

mnemostack

by udjin-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Mnemostack Search

mnemostack_search

Search indexed memories with hybrid recall to retrieve raw ranked matches, including scores, sources, and payloads, instead of a synthesized answer.

Instructions

Search indexed memories with hybrid recall.

Read-only, no side effects, no authentication required. Use this when you need raw memory matches rather than a synthesized answer. Returns a JSON object with ok, query, count, results, tokens_estimate (estimated total text tokens of the results), notes (the AUTHORITATIVE list of routine signals for stages that did not apply — e.g. temporal:no_parse on any query without a date; NOT a fault), and degraded (components that actually fell back, plus a deprecated back-compat duplicate of the routine tags until the next major; an entry absent from notes is a real fault). Results are ranked by reciprocal rank fusion of BM25, semantic, graph, and temporal retrievers when configured; each result includes id, text, score, sources, and payload. Stale facts (invalidated_at set) are hidden by default; use include_invalidated or as_of to see them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
as_ofNoPoint-in-time recall (ISO-8601): return facts valid at this world-time instant, ignoring later invalidation.
limitNoMaximum number of results to return (default 10)
queryYesNatural language question or keyword to search memories for
filtersNoPayload filters applied inside every retriever: exact match ({"tenant": "a"}) or gte/lte range ({"timestamp": {"gte": "2026-01-01"}}). Results never include points outside the filtered scope.
token_budgetNoHard cap on the total (estimated) text tokens of the returned results; the final ranking is cut to the prefix that fits. Unset uses the server-wide default, if any.
include_traceNoInclude the per-retriever recall trace (debug; verbose)
include_invalidatedNoInclude facts marked stale. Default false: memories with an invalidated_at marker are hidden from recall.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.8.0
    • addedInput schema / properties / as_of
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Point-in-time recall (ISO-8601): return facts valid at this world-time instant, ignoring later invalidation."
+}
    • addedInput schema / properties / include_invalidated
      Added value: +{
+  "default": false,
+  "description": "Include facts marked stale. Default false: memories with an invalidated_at marker are hidden from recall.",
+  "type": "boolean"
+}
    • addedInput schema / properties / token_budget
      Added value: +{
+  "anyOf": [
+    {
+      "minimum": 1,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Hard cap on the total (estimated) text tokens of the returned results; the final ranking is cut to the prefix that fits. Unset uses the server-wide default, if any."
+}
  2. Changed2 schema fields changedv0.6.0
    • addedInput schema / properties / filters
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Payload filters applied inside every retriever: exact match ({\"tenant\": \"a\"}) or gte/lte range ({\"timestamp\": {\"gte\": \"2026-01-01\"}}). Results never include points outside the filtered scope."
+}
    • addedInput schema / properties / include_trace
      Added value: +{
+  "default": false,
+  "description": "Include the per-retriever recall trace (debug; verbose)",
+  "type": "boolean"
+}
  3. Changed2 schema fields changedv0.4.3
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of results to return (default 10)"
    • addedInput schema / properties / query / description
      Added value: +"Natural language question or keyword to search memories for"
  4. First observedv0.4.1

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so: it declares read-only status, no side effects, no authentication required, default stale-fact hiding, and how to reveal stale facts. It also describes the ranking mechanism and the difference between routine notes and actual degraded components.

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?

The description is front-loaded with purpose, safety, and usage before moving into detailed return semantics. The middle section on notes, degraded, and routine signals is dense and somewhat verbose, but most sentences carry useful disambiguation. It is longer than ideal but not wasteful overall.

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?

For a seven-parameter search tool with no annotations and an output schema, the description covers the essential operational context: purpose, safety, authentication, stale-data behavior, ranking, and return structure. Nothing critical for correct invocation appears missing.

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?

Schema description coverage is 100%, so the schema already documents all seven parameters in detail. The description adds only a light restatement of stale-fact visibility for include_invalidated and as_of, but no syntax or semantic detail beyond what the schema provides. Baseline 3 is appropriate.

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 verb and resource: "Search indexed memories with hybrid recall." It also distinguishes this from mnemostack_answer by contrasting "raw memory matches" with a "synthesized answer." An agent can confidently separate this from sibling retrieval and mutation tools.

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 this when you need raw memory matches rather than a synthesized answer," naming the alternative tool's purpose directly. It also explains when to use include_invalidated or as_of to see stale facts.

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