Skip to main content
Glama
udjin-labs
by udjin-labs

mnemostack_search

Search indexed memories with hybrid recall combining keyword, semantic, graph, and temporal retrieval. Returns ranked raw matches with scores, sources, and payload.

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

Behavior5/5

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

With no annotations provided, the description carries the full transparency burden and meets it comprehensively. It discloses read-only/no side effects/no auth, ranking algorithm (RRF of BM25, semantic, graph, temporal), stale-fact defaults, and explains the semantics of notes and degraded fields, including deprecated back-compat behavior.

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 dense but well-organized, with every sentence adding meaningful detail. It flows from purpose to usage to return semantics to behavior, with no filler or 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?

This is a complex tool with 7 parameters and nuanced return fields, yet the description covers when to use it, safety profile, ranking methodology, stale handling, and how to interpret notes/degraded signals. Even though an output schema exists, the description adds necessary context about deprecation and non-fault indicators, making it fully complete.

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 description coverage is 100%, setting a baseline of 3. The description adds value beyond the schema by relating include_invalidated and as_of to stale-fact visibility and explaining how filters interact with retrievers. While not exhaustive per-parameter, it enhances understanding of parameters.

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?

Description opens with a specific verb+resource ('Search indexed memories with hybrid recall') and explicitly differentiates from the sibling answer tool: 'raw memory matches rather than a synthesized answer.' This clearly states what it does and distinguishes it from alternatives.

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?

Provides explicit when-to-use context ('Use this when you need raw memory matches rather than a synthesized answer') and indicates a read-only, no-authentication need. The synthesized-answer contrast implicitly names the mnemostack_answer sibling as the alternative.

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