Skip to main content
Glama

search_memory

Search past context by keyword across structured memory entries and freeform journal notes, optionally filtered by entry type.

Instructions

Search the memory palace by keyword.

Looks across Metis's long-term memory to recall past context — what was
decided, found, or noted before. It searches the memory_entries table
(title, summary, topics) and also greps journal/**/*.md files on disk, so
both structured memory and freeform journal notes are covered.

Args:
    query: Keyword or phrase to match against entry titles, summaries,
        topics, and journal note text.
    entry_type: Optional filter limiting results to one kind of entry —
        "session", "journal", "idea", "decision", or "topic". Empty string
        (default) searches all types.

Returns:
    A text block of matching memory entries and journal hits, or a message
    when nothing matches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
entry_typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden. It explains the search covers two sources (memory_entries table and journal files) and the return format (text block or message). No side effects or destructive behavior indicated, which is appropriate for a search tool. Some details like result limits are missing but acceptable.

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?

Well-structured with a leading sentence, explanation of coverage, and explicit Args/Returns sections. Every sentence is informative and concise.

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 the tool's complexity (two params, no nested objects) and the presence of an output schema, the description provides sufficient detail for an agent to use it correctly. Minor missing details like result ordering and pagination are not critical.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero description coverage. The description adds detailed semantics: query matches title, summary, topics, journal notes; entry_type is an optional filter with specific values listed. This fully compensates for the schema's lack of 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?

Clearly states 'Search the memory palace by keyword', specifying the verb and resource. It distinguishes from siblings by mentioning it searches both structured memory entries and journal notes, but could be more explicit about when to use this vs similar tools like search_session_memory.

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 explicit guidance on when to use this tool versus alternatives. The description describes what it does but does not provide context for choosing among similarly named 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/SVerITG/Metis'

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