Skip to main content
Glama

nexo_cognitive_retrieve

Retrieve relevant memories from STM and LTM using natural language queries, then trigger rehearsal to reinforce retention.

Instructions

RAG query over cognitive memory (STM+LTM). Triggers rehearsal on retrieved results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesNatural language query to search for
top_kNoMaximum number of results to return (default 10)
min_scoreNoMinimum cosine similarity score (default 0.5)
storesNoWhich store to search — "both", "stm", or "ltm" (default "both")both
source_typeNoFilter by source type e.g. "change", "learning", "diary" (default: all)
domainNoFilter by domain e.g. "project-a", "shopify" (default: all)
include_archivedNoIf True, also search archived memories (default False)
use_hydeNoIf True/False, force HyDE on/off. If omitted, NEXO auto-enables it for conceptual queries.
spreading_depthNoIf >0, boost co-activated neighbors directly. If omitted, NEXO may auto-enable shallow spreading for multi-hop queries.
hybrid_alphaNoWeight for vector vs BM25 fusion (default 0.6)
decomposeNoIf True, decompose complex queries into sub-queries (default True)
exclude_dreamsNoIf True, exclude dream insights from retrieval by default
exclude_dormantNoIf True, keep dormant LTM out of results unless explicitly requested
Behavior3/5

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

The description discloses that it triggers rehearsal on retrieved results, indicating a side effect beyond simple retrieval. However, with no annotations, it lacks details on permissions, state mutability, or other consequences.

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 sentences, no filler. Efficiently conveys the core purpose and an important behavioral trait.

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?

Despite no output schema, the description is too minimal for a tool with 13 parameters. It does not explain when to adjust defaults, what the return format is, or how rehearsal affects the system.

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 description coverage is 100%, so the baseline is 3. The description adds no parameter-specific information beyond what the schema already provides.

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 it performs a RAG query over cognitive memory (STM+LTM), which is a specific verb and resource. It distinguishes from siblings like nexo_cognitive_inspect or nexo_memory_recall by specifying RAG and the memory types.

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 nexo_memory_recall, nexo_recall, or nexo_ask. The description does not mention any context or exclusions.

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/wazionapps/nexo'

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