Skip to main content
Glama

search

Retrieve individual memories ranked by relevance to a query. Uses semantic search when available, otherwise keyword search, with optional cross-encoder reranking.

Instructions

Find individual memories ranked by relevance to a query. Semantic-primary when embedding models are loaded, falling back to deterministic BM25/FTS keyword search otherwise; cross-encoder reranked by default. Read-only. Returns scored, individual memory records (with ids) — use this to locate or inspect specific memories. To assemble a prompt-ready context block, use pack instead; to browse recent memories without a query, use memory_list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoRestrict to memories carrying these tags.
limitNoMaximum number of memories to return. Default 10.
queryYesNatural-language search query. Required.
spaceNoRestrict to a single memory space (namespace), or "*" for all spaces. Omit to search the default space.
rerankNoApply the cross-encoder reranker to the candidate pool. Default true.
entity_keyNoRestrict to memories linked to this entity key.
include_sourceNoIf true, reveal provenance/source metadata. Default false.
include_contentNoIf true, return each memory's full text instead of a snippet. Default false.
semantic_enabledNoForce semantic retrieval on or off. Default: on when embedding models are available, else lexical.
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses read-only nature, the dual search algorithm (semantic with fallback), cross-encoder reranking, and output format (scored records with ids). It does not mention potential side effects or rate limits, but for a search tool it is adequately 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?

Three sentences front-loaded with core purpose, followed by algorithmic nuance and sibling contrasts. Every sentence earns its place; no waste.

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 9 parameters and no output schema or annotations, the description covers key behavioral aspects (fallback, reranking, read-only) and contrasts with two siblings. It mentions output includes scored records with ids, which is helpful, but missing details about pagination or return format.

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?

Schema description coverage is 100%, so baseline is 3. The description does not add new meaning beyond the schema; it only restates that output includes ids. The schema already documents all parameters.

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 specifies the verb 'Find', the resource 'individual memories', and the ranking method. It clearly distinguishes itself from siblings by stating when to use 'pack' for context assembly and 'memory_list' for browsing without a query.

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?

The description explicitly provides when-to-use guidance ('locate or inspect specific memories') and contrasting alternatives ('use `pack` instead' for context blocks, 'use `memory_list`' for recent memories without a query).

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/teflon07/memkeeper'

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