Skip to main content
Glama
densuke
by densuke

search_memory

Search and retrieve long-term memories using hybrid search (full-text and vector) with time-decay scoring, supporting multiple AI assistants.

Instructions

ハイブリッド検索(FTS + ベクトル + RRF + 時間減衰)。

Args: query: 検索クエリ文字列。 top_k: 返す最大件数(デフォルト: 5、1 以上)。

Returns: [{"id", "score", "content", "session_id", "source", "created_at"}, ...] score の降順でソート済み。

Raises: ValueError: query が 4,096 文字を超える場合、top_k が 1 未満または 100 超の場合。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
top_kNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description fully carries the behavioral burden. It details the hybrid search method, time decay, score ordering, and exact exceptions (ValueError for invalid parameters). It does not mention read-only nature or side effects, but the context (search) implies no mutation.

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 extremely concise, using structured Markdown sections (Args, Returns, Raises). It front-loads the core hybrid search concept and uses minimal sentences with maximum information, leaving no wasted words.

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 the tool's complexity (hybrid search with multiple techniques and time decay), the description covers all essential aspects: input parameters, output format with fields and sorting, and error conditions. The output schema exists and is described, so return values are fully documented.

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%, so the description must compensate. It explains 'query' as search query string and 'top_k' as max results with default and range. Additionally, it specifies validation constraints (top_k 1-100, query max 4096) and errors, adding significant semantic value beyond the bare schema.

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 specifies 'hybrid search (FTS + vector + RRF + time decay)' stating the verb (search) and resource (memory). It distinguishes from sibling tools by naming the specific search technique, which is unique among save, list, and delete operations.

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?

The description implies use for searching memories but does not explicitly state when to use this tool versus siblings (save_memory, list_sessions, delete_memory). It lacks exclusion criteria or alternative suggestions, relying on tool names for differentiation.

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/densuke/fuga-memory'

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