Skip to main content
Glama

memory_search

Read-only

Search memories using hybrid vector and keyword matching to find semantically similar content and exact matches. Apply filters for scope, tags, date range, and temporal decay to refine results.

Instructions

Search memories using hybrid vector+keyword search. Finds semantically similar content and exact keyword matches, with optional filters for scope, department, tags, date range, and temporal decay.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query — supports natural language for semantic search and keywords for exact matching
scopeNoMemory scope for isolation
namespaceNoNamespace within scope (e.g., project name, team name)
departmentNoDepartment (e.g., legal, engineering, hr, sales, finance)
document_typeNoType of document (e.g., contract, policy, code, incident, decision)
access_levelNoAccess classification level
languageNoContent language (ISO 639-1 code)
tagsNoFilter to memories containing ALL specified tags
limitNoMaximum results to return
offsetNoSkip this many results for pagination
search_modeNoSearch mode: hybrid (vector+keyword), vector only, or keyword onlyhybrid
temporal_decayNoApply time-based decay to favor recent memories
auto_decayNoWhen true and no explicit temporal_decay is given, derive decay per result from its volatility class (volatile facts decay fast, stable facts not at all). Down-ranks stale volatile facts without hand-tuning a half-life.
date_fromNoFilter: only memories created at/after this full ISO-8601 timestamp (e.g. 2026-03-01T00:00:00Z)
date_toNoFilter: only memories created at/before this full ISO-8601 timestamp (e.g. 2026-03-31T23:59:59Z)
min_confidenceNoMinimum confidence score threshold (0-1)
min_groundednessNoMinimum TRUST threshold (0-1), distinct from min_confidence (relevance). Drops results whose groundedness — stored confidence_score + provenance tier + recency — is below this. Use to demand well-sourced memories.
as_ofNoISO 8601 point-in-time: return memories that were valid at this instant (bi-temporal). Defaults to currently-valid memories when omitted. Must be a full ISO-8601 timestamp (date + time + zone); a date-only or non-padded value is rejected to avoid a silently-wrong lexicographic slice.
use_graphNoEnable HippoRAG multi-hop recall: seed the entity graph from the query and fuse Personalized PageRank as a third ranker, surfacing memories connected through entities (associative recall) that pure vector+keyword search misses. Default false.
rerankNoEnable local cross-encoder reranking: reorder the top candidates by joint (query, document) relevance using a cross-encoder model — the biggest precision win over the bi-encoder base embedder. Slower (runs a model per candidate) and lazy-loads the model on first use. Defaults ON at the MCP server (precision matters more than latency for agent recall); pass false to skip. Left unset, programmatic callers do not rerank.
rerank_top_nNoHow many top candidates to rerank when "rerank" is true (default 50). Higher = better recall coverage but slower.
detail_levelNoControls response detail: "summary" returns titles + snippets (default, saves tokens), "full" returns complete content, "ids_only" returns just IDs and titles for browsingsummary
max_tokensNoApproximate maximum response size in tokens (~4 chars per token). Results are truncated to fit within budget. Applies after detail_level projection.
Behavior4/5

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

Annotations indicate readOnlyHint=true, which is respected. The description adds behavioral context beyond annotations by mentioning hybrid vector+keyword search, optional filters, and temporal decay. No contradictions.

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 (2 sentences, ~30 words), front-loaded with the core functionality, and avoids unnecessary details. Every sentence adds value.

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?

Given the complexity (23 parameters, nested objects) and rich schema coverage, the description provides a good high-level summary. It covers key features but could briefly mention reranking or auto_decay. However, schema handles most details, so completeness is adequate.

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?

Input schema provides 100% description coverage for all 23 parameters. The description adds a high-level overview but does not significantly enhance understanding beyond what the schema already offers. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool searches memories using hybrid vector+keyword search and lists optional filters. It distinguishes the action and resource well, but does not explicitly differentiate from sibling tools like memory_query or memory_get.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or comparison to other search or retrieval tools.

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/YonasValentin/mcp-memory-graph'

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