Skip to main content
Glama

search_memory

Retrieve relevant past memories by semantic similarity search to inform current tasks, with optional temporal, category, and relationship filtering.

Instructions

Search indexed memories by semantic similarity and return ranked results with optional temporal filtering. Read-only, but may fire stored reminders as a side effect. Use proactively at the start of tasks, when debugging, writing, or when the user references past work.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query — natural language or keywords
limitNoMax results to return
scopeNoOptional explicit scope
sessionIdNoOptional session identifier to infer session:<id> scope
allScopesNoWhen true, explicitly allow cross-scope search
categoryNoFilter by memory category: profile (identity/background), preferences (habits/style), entities (projects/tools/people), events (past happenings), cases (problem-solution pairs), patterns (reusable workflows)
profileNoRetrieval profile
renderNoResult rendering mode: verbatim (default, original order) or highlight (reorder by contextual relevance to query)verbatim
afterNoFilter memories stored after this date (ISO format YYYY-MM-DD, or relative like '最近30天', 'last 7 days')
beforeNoFilter memories stored before this date (ISO format YYYY-MM-DD, or relative)
graphNoEnable KG graph traversal (PPR) for relationship-aware search. Use when query involves entity relationships (e.g. 'what tools does Alice use', 'Bob的朋友').
includeArchivedNoWhen true, also return archived/superseded/consolidated memories (default: only active)
detail_levelNoResult detail level: brief (ID+score+one-liner), normal (default, current behavior), full (include metadata)normal
topicTagNoFilter by topic tag (e.g. 'auth', 'deploy', 'testing'). Only returns memories tagged with this topic.
reconstructNoReturn LLM-synthesized reconstruction alongside raw results. Requires RECALLNEST_CONSTRUCTIVE_RETRIEVAL=true.
validAtNoQuery memories valid at a specific point in time (ISO date, e.g. '2025-06-15'). Returns only memories whose validity window covers this date.
includeExpiredNoWhen true, include expired memories in results (demoted 80%). Default: only active/non-expired.
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool is read-only but may fire stored reminders as a side effect. However, it does not describe other potential behaviors such as authorization needs, rate limits, or edge cases related to its many parameters.

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 extremely concise: two sentences defining purpose and behavior, plus one sentence for usage guidelines. All content is front-loaded and no words are wasted.

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

Completeness2/5

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

Despite having 17 parameters, no output schema, and no annotations, the description does not explain important aspects like return format, how to use complex parameters (e.g., 'graph', 'reconstruct', 'validAt'), or provide examples. The agent may be underinformed.

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 each parameter is already documented. The description adds no additional parameter-level details beyond 'semantic similarity' and 'temporal filtering', which align with 'query' and date parameters. 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 clearly states 'Search indexed memories by semantic similarity and return ranked results with optional temporal filtering.' It uses a specific verb ('search') and resource ('memories'), and distinguishes from sibling tools like 'store_memory' or 'forget_memory' by focusing on retrieval.

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

Usage Guidelines4/5

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

The description includes explicit usage guidance: 'Use proactively at the start of tasks, when debugging, writing, or when the user references past work.' This tells the agent when to invoke. It does not explicitly exclude alternatives like 'brief_memory', but the context is clear.

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/AliceLJY/recallnest'

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