Skip to main content
Glama

mnemostack_search

Search indexed memories with hybrid recall, combining BM25, semantic, graph, and temporal retrievers for ranked results.

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), and degraded (which components fell back while serving the call; empty when healthy). 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

Behavior5/5

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

The description fully covers behavioral traits: read-only, no side effects, no authentication required. It explains the return object structure, ranking method (reciprocal rank fusion), and handling of stale facts. Since no annotations are provided, the description carries the full burden and does so excellently.

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 concise and well-structured: first sentence states purpose, second paragraph details behavior and output, and it includes usage guidelines. Every sentence adds value with no redundancy.

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 the tool's complexity and the presence of an output schema, the description is complete. It covers purpose, usage, behavior, output structure, ranking, and parameter hints, making it sufficient for an AI agent to select and invoke the tool correctly.

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% and the schema descriptions are detailed. The description adds context about how parameters like as_of, include_invalidated, and token_budget affect retrieval and output, but the added value is moderate given the thorough 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 'Search indexed memories with hybrid recall' and distinguishes from siblings by specifying 'raw memory matches rather than a synthesized answer,' which contrasts with mnemostack_answer.

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?

Explicitly says 'Use this when you need raw memory matches rather than a synthesized answer,' providing clear guidance on when to use this tool over alternatives. Also notes it is read-only with no side effects or authentication.

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/udjin-labs/mnemostack'

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