Skip to main content
Glama

session_search_memory

Search past sessions by semantic meaning using vector embeddings to find relevant context when keyword searches fail or wording differs.

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
queryYesNatural language search query describing what you're looking for.
projectNoOptional: limit search to a specific project.
limitNoMaximum results to return (default: 5, max: 20).
similarity_thresholdNoMinimum similarity score 0-1 (default: 0.7). Higher = more relevant, fewer results.
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.
activationNoConfiguration for ACT-R inspired Spreading Activation. Use this to find structurally related memories beyond direct semantic/keyword hits.
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses vector embedding mechanism, pgvector dependency, and advanced features like ACT-R spreading activation and memory trace metadata. Missing only error handling or rate limit details.

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?

Two tightly structured sentences. First establishes mechanism and requirements; second provides usage guidelines. Zero redundancy—every clause conveys distinct information about functionality, prerequisites, or sibling relationships.

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?

Comprehensive for a complex 7-parameter tool with nested objects. Covers search mechanism, infrastructure requirements, and sibling differentiation. Minor gap: no output description (relevant since no output schema exists), though enable_trace parameter partially hints at return structure.

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

Parameters3/5

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

Schema coverage is 100%, establishing baseline 3. Description provides conceptual context (semantic vs keyword) that supports understanding the query parameter and mentions spreading activation, but does not add significant parameter-specific semantics beyond what the schema already documents.

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?

States specific verb ('Search') and resource ('session history semantically'), clearly distinguishing from keyword-based alternatives. Explicitly contrasts vector embeddings vs exact wording matching, establishing precise scope.

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 when-to-use guidance ('use this when keyword search returns no results or when the query is phrased differently') and names the specific alternative tool (knowledge_search). Also notes prerequisite (pgvector extension).

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/BCBA'

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