Skip to main content
Glama

Recall memories

recall
Read-onlyIdempotent

Search long-term memory using natural language queries. Filter by tags, types, collections, and visibility to retrieve stored information from past interactions.

Instructions

Search long-term memory. Call list_collections when scope is unclear. For GitHub/Notion synced content use collection project: (unified per project) or tags github/notion. Connect at dashboard.memxus.com/integrations. After this tool returns, show the user the pre-rendered block at the end of the tool result verbatim (user_facing_template). Do not repeat the raw context_block. Expand context: if count < total, recall/get_context with exclude_memory_ids + higher max_memories; if count === total, say no more memories without calling the server. Skills: use N → use_skill_in_chat, install N → install_skill, skip N → skip_skill.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoOptional tags. A tag like project:my-app also sets collection automatically.
typeNoMemory category: general, preference, fact, instruction, or conversation. Omit to include all types.
limitNoMax results. Omit for server default (10). Capped per your plan on the server.
queryYesNatural-language search query (e.g. "Henry project stack", "user prefers dark mode").
group_idNoUUID of a shared group. Required with visibility=shared when group_name is not set.
collectionNoScope slug (e.g. project:memxus, personal:preferences). GitHub/Notion connector syncs use project:<slug> — one collection per project. Partial names work; call list_collections when unsure.
group_nameNoExact group name (case-insensitive). Alternative to group_id for shared memories.
visibilityNoOptional. Defaults to user dashboard preference (private unless include_group_memories_in_context is on).
include_skillsNoWhen skill routing is enabled, append official skill suggestions for work intents (build/review/fix/test). Default: auto-detect from query.
exclude_memory_idsNoMemory IDs to exclude (for "Ampliar el contexto" follow-up calls).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of memories returned.
totalNoTotal eligible memories for ranking (before LIMIT).
messageYesHuman-readable summary (same as content text).
memoriesYesMatching memories, ordered by relevance.
tokens_usedNoEstimated tokens in the injected response.
impact_summaryNo
skills_messageNoFormatted skills block when skill routing is active.
suggested_skillsNoOptional skill suggestions when skill routing is active.
impact_summary_textNoToken reuse line for the AHORRO block when ENABLE_IMPACT_SUMMARY is on.
Behavior4/5

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

Annotations already indicate readOnly=true, idempotent=true, destructive=false. The description adds context on result handling (user_facing_template, expand context logic) and integration details, which aids agent behavior beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long and includes multiple distinct instructions (post-processing, skills, integration link). While informative, it lacks conciseness and could be better structured into separate guidance sections.

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?

Given the tool's complexity (10 params, output schema exists), the description covers scope clarification, integration, parameter usage, and result handling comprehensively. No gaps identified.

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 parameters are already described. The description adds value by explaining the automatic collection setting via tags and providing examples for collection usage, improving clarity.

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 opens with 'Search long-term memory', a clear verb+resource statement. It distinguishes from siblings like 'list_collections' and 'forget' by specifying its role as a search mechanism.

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?

Provides explicit guidance: 'Call list_collections when scope is unclear' and specifies use of collection slugs for GitHub/Notion content. Includes post-processing steps but lacks explicit when-not-to-use clauses.

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/gpitrella/memxus-remote-mcp'

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