Skip to main content
Glama

Search memories

memory_search
Read-onlyIdempotent

Find project facts, decisions, and patterns using ranked full-text search across SQLite and file memories, with optional Obsidian integration and progressive detail levels.

Instructions

Ranked full-text + decay-weighted search across SQLite, file-memory sources, and (when configured) the Obsidian vault. Read-only. Use the three-layer progressive-disclosure pattern: detail="index" (~30 tok/result, start here), "summary" (~80 tok), "full" (~150-300 tok, use sparingly). Follow-ups: memory_timeline(id) for chronological neighbours of one hit, memory_get(id) for one full body, memory_graph(id) to explore typed edges.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesFree-text query. Tokenised by FTS5; phrases match individual terms. Examples: `"oauth refresh"`, `"why we picked postgres"`.
project_pathNoOptional absolute project path to scope results. Empty string searches across all projects (subject to scope rules).
memory_typeNoOptional type filter, e.g. `decision`, `lesson`. Empty string returns all types.
limitNoMaximum number of results to return (1-50). Default 10.
detailNoDisclosure level — `index` (cheapest), `summary`, or `full`. Always start at `index` and escalate only if needed.index
include_file_memoriesNoIf true (default), also search markdown memory files registered as sources. Set false to limit to SQLite + vault.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesEcho of the query that was executed.
detailYesDisclosure level used to render this result set.
countYesNumber of SQLite/file results returned (after `limit` is applied).
resultsYesRanked SQLite/file hits.
vault_resultsYesObsidian vault matches (separate from SQLite results). Always an array — empty when the vault is disabled or has no matches.
total_tokensYesEstimated token cost of the rendered text payload.
Behavior4/5

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

Annotations already provide readOnlyHint=true and idempotentHint=true. Description adds context about search ranking, decay-weighting, and data sources beyond the annotations. No contradiction.

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?

Extremely concise: two sentences plus a follow-up instruction. All information is front-loaded and relevant, with no wasted words.

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 presence of an output schema, the description does not need to explain return values. It covers core behavior, sources, usage pattern, and follow-up tools comprehensively for a search tool.

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 is 3. The description adds value by giving token size estimates for detail levels and query examples (e.g., 'oauth refresh'), which are not in the schema.

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 performs ranked full-text search across multiple sources and is read-only. It distinguishes from siblings by naming specific follow-up tools and implying this is the primary search entry point.

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?

Explicitly provides a three-layer progressive-disclosure pattern with token estimates and instructs to start at 'index'. Names alternative tools for deeper exploration (timeline, get, graph), telling the agent when to use this tool vs others.

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/lfrmonteiro99/memento-mcp'

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