Skip to main content
Glama

semantic_search

Search your personal memory layers by combining vector similarity with keyword matching to retrieve relevant episodic, semantic, and procedural memories.

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
layersNoepisodic,semantic,procedural
top_kNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Without annotations, the description fully carries the burden, detailing the 5-step retrieval pipeline, RRF fusion (k=60), deduplication, and return format. No contradictions.

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?

Well-structured with summary, context, pipeline, and Args, but slightly verbose; still every sentence serves a purpose.

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?

Covers purpose, alternatives, pipeline, parameters, and return format comprehensively for a complex tool with fusion.

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?

Schema has 0% description coverage, but the description's Args section explains each parameter with defaults and allowable values, compensating fully.

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?

The description clearly states 'Search across memory layers using vector similarity + keyword RRF fusion,' specifies the exact resource (personal MEMORY layers), and distinguishes from siblings like 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?

Explicitly provides when to use (searching memory) and when not (use search_pdf_knowledge for documents, search_library for metadata), offering clear alternatives and context.

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