Skip to main content
Glama

recall

Search persistent memory by semantic meaning to answer specific questions. Retrieves ranked memories using hybrid vector, text, and graph search with relevance scoring.

Instructions

Search persistent memory by meaning, returning the most relevant past memories ranked by semantic similarity. This is a read-only operation that runs a 4-way hybrid search (vector similarity, BM25 full-text, entity graph traversal, temporal proximity) and reranks results with a cross-encoder model. Use recall (not context) when you need to answer a specific question: "what language does the user prefer?", "how was auth implemented?", "what was decided about the database?". Do not use for broad session bootstrapping (use context instead). Returns up to limit memories with relevance scores (0-1). Costs 1 operation per call. If no memories match, returns an empty list, not an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesNatural language search query. Semantic, not keyword-based: 'what programming language does the user prefer?' works better than 'language preference'. More specific queries return more relevant results.
agent_idNoAgent instance identifier. Must match the agent_id used when storing memories. Default: 'default'.default
user_idNoUser identifier. When provided with scope 'user', also searches user-scoped memories shared by other agents.
scopeNoSearch scope. 'agent' (default): only this agent's memories. 'user': also includes memories shared to user scope. 'org': includes org-wide memories. Broader scope returns more results but may include less relevant memories.
tagsNoFilter results to only memories with at least one matching tag. Omit to search all memories regardless of tags.
limitNoMaximum memories to return, 1-20. Default 5. Use higher values (10-20) for broad searches, lower (1-3) for targeted lookups.
Behavior5/5

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

No annotations provided, yet description comprehensively discloses: read-only nature, 4-way hybrid search algorithm details, reranking method, cost ('1 operation per call'), return format (relevance scores 0-1), and error handling (empty list vs error).

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?

Seven sentences follow a logical progression: purpose → mechanism → usage (+examples) → exclusions → returns → cost → errors. Every sentence earns its place; technical details (hybrid search) are justified given lack of annotations/output schema.

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?

No output schema exists, yet description fully compensates by detailing return structure (memories with relevance scores 0-1) and edge case behavior. Covers all necessary aspects for a 6-parameter semantic search tool.

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% so baseline is 3. Description adds value by referencing 'limit' in return context ('Returns up to limit memories') and reinforcing query semantics through natural language examples, justifying the elevated score despite comprehensive 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?

Opens with specific verb+resource ('Search persistent memory by meaning') and explicitly distinguishes from sibling tool 'context' via contrasting use cases. The semantic similarity mechanism is clearly stated.

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 ('when you need to answer a specific question' with examples) and when-not-to-use ('Do not use for broad session bootstrapping') guidance, naming the specific alternative tool ('use context instead').

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/AlekseiMarchenko/central-intelligence'

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