Skip to main content
Glama
prefrontal-systems

Mnemex

by prefrontal-systems
OverviewSchemaRelated ServersScoreDiscussions
Local

search_unified

Search across short-term and long-term memory with unified ranking, using customizable weights and filters to retrieve relevant information from temporal data stores.

Instructions

Search across both STM and LTM with unified ranking.

Args:
    query: Text query to search for.
    tags: Filter by tags.
    limit: Maximum total results.
    stm_weight: Weight multiplier for STM results.
    ltm_weight: Weight multiplier for LTM results.
    window_days: Only include STM memories from last N days.
    min_score: Minimum score threshold for STM memories.

Returns:
    A dictionary containing the search results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
ltm_weightNo
min_scoreNo
queryNo
stm_weightNo
tagsNo
window_daysNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'unified ranking' but doesn't explain what this means operationally, how results are combined, or any behavioral traits like performance characteristics, error conditions, or limitations. The description is minimal beyond basic functionality.

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 efficiently structured with a clear purpose statement followed by organized parameter and return sections. Every sentence earns its place, and the information is front-loaded with the core functionality stated first.

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?

Given the tool's complexity (7 parameters, no annotations) but with an output schema present, the description covers parameters adequately but lacks behavioral context. It doesn't explain how STM and LTM differ, what 'unified ranking' entails, or provide usage examples. The output schema handles return values, but more operational guidance would be helpful.

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?

With 0% schema description coverage, the description compensates well by listing all 7 parameters with brief explanations. It clarifies what each parameter controls (e.g., 'Weight multiplier for STM results', 'Only include STM memories from last N days'), adding meaningful context beyond the schema's type information.

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 clearly states the tool searches across STM and LTM with unified ranking, providing a specific verb ('search') and resources ('STM and LTM'). However, it doesn't explicitly differentiate from sibling tools like 'search_memory' or 'open_memories', which appear related to memory operations.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'search_memory' or 'open_memories'. The description only states what the tool does, not when it's appropriate or what distinguishes it from similar tools in the sibling list.

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/prefrontal-systems/mnemex'

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