Skip to main content
Glama

search_soul_memory

Retrieve semantically relevant text chunks from a soul's workspace files to ground responses in its actual memories, personality, and backstory.

Instructions

Semantic search across indexed soul memory.

Finds the most relevant chunks of text from the soul's workspace files based on meaning, not just keywords. Useful for grounding responses in the soul's actual memories, personality, and backstory.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesWhat to search for (natural language).
workspace_pathNoPath to soul workspace. Defaults to current workspace.
top_kNoNumber of results to return (1-20, default 5).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description fully explains behavior: semantic search returning text chunks from workspace files. Does not detail edge cases or limitations, but sufficient for typical use.

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?

Three sentences, each serving a clear purpose: title, function, and use case. No wasted words.

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?

With an output schema present, description does not need to explain return format. It adequately covers purpose and usage context, though it could mention dependency on prior indexing.

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% with clear parameter descriptions, so description adds no additional detail beyond what the schema already provides.

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?

Description clearly states it performs semantic search across indexed soul memory, using 'finds the most relevant chunks... based on meaning, not just keywords', which distinguishes it from keyword-based tools like memory_recall.

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

Usage Guidelines4/5

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

Explicitly states it is 'useful for grounding responses in the soul's actual memories, personality, and backstory', giving clear context for when to use it, though it does not mention when not to use or alternatives.

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/sailorpepe/undesirables-mcp-server'

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