Skip to main content
Glama

session_search_memory

Search session history by meaning using vector embeddings to find contextually similar sessions, even when exact wording differs. Use when keyword search returns no results or query phrasing varies.

Instructions

Search session history semantically (by meaning, not just keywords). Uses vector embeddings to find sessions with similar context, even when the exact wording differs. Requires pgvector extension in Supabase.

Complements knowledge_search (keyword-based) — use this when keyword search returns no results or when the query is phrased differently from stored summaries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum results to return (default: 5, max: 20).
queryYesNatural language search query describing what you're looking for.
projectNoOptional: limit search to a specific project.
activationNoConfiguration for ACT-R inspired Spreading Activation. Use this to find structurally related memories beyond direct semantic/keyword hits.
enable_traceNoIf true, returns a separate MEMORY TRACE content block with search strategy, latency breakdown (embedding vs storage), and scoring metadata. Default: false.
context_boostNoIf true, appends current project and working context to the search query before embedding generation, naturally biasing results toward contextually relevant memories. Useful when searching within a specific project context. Default: false.
similarity_thresholdNoMinimum similarity score 0-1 (default: 0.7). Higher = more relevant, fewer results.
Behavior4/5

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

No annotations provided, but the description discloses the semantic search mechanism, vector embedding usage, and optional trace feature. It does not explicitly state read-only behavior, but that is implied. Overall, it provides good behavioral context beyond the bare minimum.

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?

The description is three sentences, front-loaded with purpose and mechanism, followed by prerequisites and usage guidance. Every sentence adds value with no redundant or unnecessary content.

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?

The description explains purpose, mechanism, and usage well but does not describe the return format or structure of results. Given that there is no output schema, a brief note on what the tool returns would improve completeness.

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 100%, but the description adds valuable context for parameters like activation (ACT-R spreading activation) and context_boost (biasing toward contextual relevance), enhancing understanding beyond the schema definitions.

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 the tool searches session history semantically using vector embeddings, distinguishing from keyword-based search. The verb 'Search' and resource 'session history' are specific and unambiguous.

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 tells when to use this tool vs the sibling `knowledge_search` (keyword-based) — use when keyword search fails or query phrasing differs. Also mentions requirement of pgvector extension, providing clear guidance.

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/dcostenco/prism-coder'

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