Skip to main content
Glama

Metis · Memory Curator — Semantic Search

semantic_search

Retrieve relevant personal memories by searching across episodic, semantic, and procedural layers using vector similarity and keyword matching fused via reciprocal rank fusion.

Instructions

Search across memory layers using vector similarity + keyword RRF fusion.

Searches your personal MEMORY layers (episodic/semantic/procedural — things
you or Metis recorded), NOT your document library. For documents/PDFs use
search_pdf_knowledge; for reference metadata use search_library.

Retrieval pipeline (M5.8):
1. Embed the query.
2. Run vector similarity search on each requested layer.
3. Run keyword LIKE search on each layer.
4. Fuse results using Reciprocal Rank Fusion (RRF, k=60).
5. Return top_k deduplicated results ranked by fused score.

Args:
    query: Natural language search query to embed and keyword-match.
    layers: Comma-separated memory layers to search, drawn from 'episodic',
        'semantic', and 'procedural'.
    top_k: Number of fused results to return (default 5).

Returns:
    A single TextContent listing the top fused results (layer, title, score,
    timestamp, and a content preview), or a "no results" / error message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
top_kNo
layersNoepisodic,semantic,procedural

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided; description fully discloses the retrieval pipeline (embedding, vector search, keyword search, RRF fusion, dedup), scope constraints, and the fact that it returns fused results.

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 summary, restrictions, pipeline details (step-by-step), and parameter documentation. Every sentence adds value without redundancy.

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 3 parameters and an output schema, the description covers the retrieval process, scope, parameters, and return format completely, leaving no gaps for an agent to misunderstand.

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 coverage is 0%, but the description includes an Args section that explains each parameter (query, layers, top_k), their types, defaults, and for layers the allowed values. Could be slightly more precise about layers format but adds significant value.

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?

Clearly states it searches across memory layers using vector similarity and RRF fusion, and explicitly distinguishes from sibling tools search_pdf_knowledge and search_library.

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?

Provides explicit guidance on when to use (personal memory layers) and when not to use (document library), with clear alternatives for other use cases.

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