Skip to main content
Glama

recall_memories

Use semantic search to retrieve relevant memories from past sessions. Filter by scope, type, category, or importance to narrow results.

Instructions

Search stored memories using semantic search. Returns memories ranked by relevance, importance, and recency. Use this to find relevant context from past sessions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesWhat to search for (natural language)
scopeNoFilter by scopeall
limitNoMax results
memory_typeNoFilter by type
categoryNoFilter by category (e.g., "backend", "frontend", or any custom category)
importance_minNoOnly return memories with importance >= this value
tagNoFilter by tag (e.g., "marketing-campaign")
team_idNoOptional override. Team memories are automatically included for team/enterprise users.
context_typeNoOptional context type that shifts scoring weights. debugging = boost bug/pattern memories, planning = boost architecture/decision, reviewing = boost pattern/preference.
synthesizeNoWhen true and 3+ results are found, returns an AI-synthesized summary combining all memories into a coherent answer.
Behavior3/5

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

The description mentions semantic search and ranking criteria (relevance, importance, recency) but does not explicitly state that the tool is read-only or disclose potential side effects. Given no annotations, the description carries the full burden, and while adequate, it leaves some behavioral traits implicit.

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 two sentences: the first explains the action and ranking, the second gives usage guidance. No unnecessary words, efficiently conveying purpose and usage.

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 (10 parameters, no output schema), the description covers the main purpose and filtering capabilities. It could include return format or pagination details but is sufficient for a search tool with clear schema descriptions.

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?

The input schema has 100% coverage with detailed descriptions for all 10 parameters. The main description adds minimal parameter-specific meaning beyond stating 'semantic search' and ranking criteria. With full schema coverage, baseline score of 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 the tool performs semantic search on stored memories and returns results ranked by relevance, importance, and recency. It distinguishes itself from siblings like list_memories (listing all) by focusing on semantic retrieval for context from past sessions.

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 explicitly says 'Use this to find relevant context from past sessions,' providing clear usage guidance. It does not explicitly mention when not to use it or alternatives, but the context among siblings implies its specific role.

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/hifriendbot/cogmemai-mcp'

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