Skip to main content
Glama

recall

Retrieve memory documents from labeled MemorySinks filtered by provenance and recency, returning citation packets for knowledge assembly.

Instructions

Retrieve memory documents from one or more labeled MemorySinks, filtered by provenance (min_confidence, types, max_age_days) and ranked by recency (observed_at DESC). Returns citation packets (doc_id, source_handle, title, heading_path, mtime, hash, display_url, properties) — the same 8-field shape Phase 3 assembly tools use. Superseded documents are hidden by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesNatural-language query; routes through hybrid (semantic + BM25) search
min_confidenceNoExclude docs whose confidence ordinal is lower than this (direct=3, inferred=2, uncertain=1)
typesNoRestrict to docs whose `type` property is in this set
max_age_daysNoExclude docs whose `observed_at` is older than this many days
sinkNoMemory sink name OR full obsidian-fs://… handle. Defaults to all configured sinks.
limitNoMaximum results AFTER filter+sort; default 20
vaultsNoRestrict to these vault names; defaults to all configured
Behavior4/5

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

No annotations exist, so the description carries the full burden. It discloses the return shape (8 fields), default hiding of superseded documents, filtering parameters, and ranking by recency. However, it omits details like rate limits, authentication requirements, or error handling.

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?

Two sentences: the first covers purpose, filtering, and ranking; the second covers return format and default behavior. It is efficiently front-loaded with 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?

For a tool with 7 parameters and no output schema, the description explains the return shape and default behavior. It lacks pagination details beyond the limit parameter and does not mention error handling or empty result behavior.

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 the baseline is 3. The description adds value by explaining ranking by recency (observed_at DESC) and the return shape (citation packets), which are not in the schema. This helps the agent understand the output structure.

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 specifies the verb 'retrieve', the resource 'memory documents from MemorySinks', and details filtering and ranking. It distinguishes from sibling search tools by emphasizing MemorySinks and citation packets.

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

Usage Guidelines3/5

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

The description implies usage for retrieving memory documents but does not explicitly state when to use this tool versus alternatives like search_hybrid or search_text. No when-not-to-use guidance is provided.

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/owrede/vault-memory'

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