Skip to main content
Glama

search_memory

Search your research memory by keyword across titles, summaries, topics, and markdown journal files. Filter results by session, journal, idea, decision, or topic.

Instructions

Search the memory palace by keyword.

Searches the memory_entries table (title, summary, topics) and performs a
filesystem grep across journal/**/*.md files.

Args:
    query: Search keyword or phrase.
    entry_type: Optional filter -- "session", "journal", "idea", "decision", "topic".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
entry_typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses dual search scope (database + filesystem grep) but lacks details on performance, pagination, or behavior on no results.

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?

Description is brief with a structured Args section. Front-loads main purpose. Could be slightly more organized but effectively communicates the core behavior.

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?

Output schema exists, so return values not required. Covers parameters and search scope. Lacks details on result format, sorting, or limits, which would be helpful 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 0%, but the description adds a clear explanation for both parameters, including allowable values for entry_type. This compensates for the missing schema descriptions.

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 it searches by keyword across the memory_entries table and journal files. It provides specific resources (table, filesystem) but does not explicitly differentiate from sibling search tools like search_session_memory or search_fulltext.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. No exclusions or prerequisites mentioned.

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/SVerITG/Metis'

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