Skip to main content
Glama

recall

Search memories by text or entity name. Results are re-ranked by relevance, heat, and importance, with explanations. Use at task start to recall prior work.

Instructions

Retrieve memories relevant to the current context using full-text search (BM25) + entity-name match, re-ranked by a composite score (relevance × heat × momentum × importance). Returns only what fits in the token budget, with match_reasons explaining WHY each memory was returned. Opportunistically refreshes stale momentum scores for entities in the result set. Supports pagination via offset/has_more. Layer aliases accepted. Use at the start of any task that might involve prior work.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesWhat you want to remember (free-text, entity name, or FTS5 MATCH expression)
entity_nameNoOptional — narrow to a specific entity
layerNoOptional layer filter. Accepts aliases (decisions/warnings/how/etc.) as well as canonical names.
bandNoOptional — only return memories whose heat_band matches.
max_tokensNoApprox token budget. Default 2000. Either max_tokens or limit stops iteration (whichever fires first).
limitNoOptional hard cap on number of memories. Stops at min(max_tokens-budget, limit).
offsetNoSkip this many top results (pagination). Use has_more from prior response to decide next offset.
mark_accessedNoSet false for preview / listing queries that should not bump heat.
Behavior5/5

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

No annotations provided, but the description fully covers behavioral aspects: search method (BM25+entity), re-ranking composite score, token budget, match_reasons, pagination, and side effect of refreshing stale momentum scores. This is highly transparent.

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?

Four concise sentences, each adding significant information. Starts with core action, then details, then usage guidance. No wasted words.

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?

Covers retrieval mechanism, ranking, token budget, match_reasons, side effect, pagination, layer aliases, and usage context. Lacks explicit description of return format (fields of memory objects), but given no output schema, it mentions match_reasons, which is key. Still fairly complete.

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 description coverage is 100%, so baseline 3. The description adds value by explaining the composite score, pagination using has_more, layer alias acceptance, and the token budget mechanism, which enrich understanding beyond individual parameter descriptions.

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 it retrieves memories using full-text search and entity-name match, with specific re-ranking. It distinguishes from siblings by focusing on relevance to current context and mentions 'Use at the start of any task that might involve prior work', providing clear purpose.

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?

Explicitly says when to use ('at the start of any task that might involve prior work'). However, it does not mention when not to use or provide explicit alternatives among siblings. Still, 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/michielinksee/linksee-memory'

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