Skip to main content
Glama

search_episodes

Search raw episodic conversation turns using full-text search, synonym expansion, and optional vector matching to retrieve relevant past dialogue from shared memory.

Instructions

Search raw episodic conversation turns (FTS5 + synonym expansion + optional vectors).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_episodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
session_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden, and it does disclose that matching is FTS5 + synonym expansion + optional vectors — useful for understanding that results are lexical/fuzzy rather than exact. It says nothing about ranking, score fields, result caps, or what happens when the vector index is unavailable, so behavioral coverage remains partial.

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?

A single front-loaded sentence with no filler, and the mechanism is parenthetically placed after the core action. It is arguably too terse given three undocumented parameters, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be explained, but with no annotations and 0% parameter coverage the description leaves query syntax, session scoping, and result limits unaddressed. For a search tool where query construction drives success, this is a significant shortfall.

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

Parameters2/5

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

Schema description coverage is 0% for three parameters (query, limit, session_id), and the description adds no meaning to any of them. It does not explain query syntax for FTS5, the default limit of 5, or that session_id scopes to one conversation — the most decision-relevant gap for a search tool.

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?

The description gives a specific verb and resource ('Search raw episodic conversation turns') plus the retrieval mechanism (FTS5 + synonym expansion + optional vectors), which implicitly separates it from fact/reference search siblings. It never names an alternative explicitly, so the differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Raw episodic conversation turns' implies a use case (verbatim dialogue recall rather than fact lookup), which is enough for an agent to guess when to pick this over search_facts. However, there is no explicit when-to-use rule, no exclusion, and no stated alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.