Skip to main content
Glama
thuupx

memory-mcp-lite

by thuupx

Search memories (compact candidates)

search_memory_light
Read-onlyIdempotent

Searches atomic memories by free-text query to find relevant candidates when summaries are insufficient. Returns compact records for follow-up with get_memory_detail.

Instructions

Lexical FTS5 search across atomic memories. Returns compact candidate records only — not full content. USE WHEN: the summary tools above do not provide enough context AND the request includes a concrete search phrase (command name, symbol, past event). DO NOT USE WHEN: summaries already answer the question, the query is empty/too vague, or you only need the global/project/task summary. CALL ORDER: always call summary tools first. Then follow up this tool's top 1-3 results with get_memory_detail — never dump all candidates. RETURNS: { count, results: [{ id, title, summary, memory_type, level, importance, updated_at }] }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax candidate results, 1-20. Defaults to 10.
queryYesFree-text search query — a keyword, command, or phrase
scopeNoSearch scope: 'project' (scoped to resolved project) or 'global' (all projects).project
git_rootNoAbsolute path to the git repository root
project_idNoExplicit project id
remote_urlNoGit remote URL
workspace_pathNoAbsolute path to the workspace root

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
resultsYes
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds that it returns compact candidates (not full content) and describes the return shape. Provides search type (FTS5) and call-order context.

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?

Concise, well-structured with labeled sections. Every sentence is informative; 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 output schema (in description), good annotations, and full schema coverage, the description fully informs the agent about behavior, usage, and results.

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 3 is appropriate. The description does not add extra meaning beyond schema descriptions, but does not need to.

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?

Description clearly states it's a lexical FTS5 search across atomic memories and that it returns compact candidate records, not full content. Distinct from siblings like get_memory_detail.

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?

Explicit WHEN, DO NOT USE, and CALL ORDER sections. Specifies when to use (summaries insufficient + concrete search phrase) and when not, and prescribes calling summary tools first then get_memory_detail for top results.

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/thuupx/memory-mcp-lite'

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