Skip to main content
Glama

memo_search

Read-onlyIdempotent

Retrieve durable memories by text, vector similarity, or hybrid search. Filter by source, date, type, and file to get IDs, tags, and excerpts.

Instructions

Search durable memories by text, vector similarity, or hybrid mode.

Read-only. Use for direct retrieval when you need source records, ids, dates, tags, or excerpts. mode accepts hybrid, vec, or bm25; body_chars controls snippet length, and source attributes consult logging.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNo
modeNohybrid
typeNo
whenNo
limitNo
queryYes
sourceNo
date_toNo
explainNo
date_fromNo
body_charsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

The description reinforces the read-only nature indicated by annotations, and adds behavioral details about parameter semantics (mode, body_chars, source logging). No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (3 sentences) and front-loaded: purpose first, then usage, then key param details. No redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 11 parameters and an output schema, the description covers core behavior (search modes, snippet control, filtering) but omits details on other parameters like type, when, date range, explain, etc. Adequate for a high-level overview but not fully comprehensive.

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?

With 0% schema description coverage, the description helps by explaining three parameters (mode, body_chars, source) but leaves 8 parameters undocumented. The provided explanations are helpful but incomplete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool 'searches durable memories' using text, vector, or hybrid modes. It specifies the verb and resource, though it does not explicitly differentiate from sibling tools like memo_search_trace.

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?

The description provides a clear usage scenario: 'Use for direct retrieval when you need source records, ids, dates, tags, or excerpts.' It frames the tool as a read-only retrieval option, but does not mention when to avoid it or alternative tools.

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/jagoff/memo'

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