memory_explore
Explore a knowledge map of entities and relationships with query-scoped chunks, giving a high-level overview instead of raw memory results.
Instructions
Explore a knowledge map of entities, with query-scoped chunks per entity (LLM-free).
REQUIRES A POPULATED ENTITY GRAPH — returns {"entities": [], "count": 0} otherwise, for every query. Check with memory_graph {"action": "list_entities"}; populate with memory_quality {"action": "maintain", "dry_run": false} (dry_run defaults to true and stores nothing). Unavailable on the Cloudflare backend. Guide: docs/guides/token-efficient-retrieval.md
USE THIS WHEN:
User wants a high-level overview ("what do I know about X", "map out", "explore")
Need entities + their relationships rather than raw memory chunks
Building a knowledge graph view or entity dashboard
Returns a list of entities. Per entity:
entity_id: canonical slug (NFKD-normalized, hash fallback for non-Latin scripts)
name, entity_type
summary: extractive (LLM-free) summary from top chunks
relation_count: number of graph relationships
top_chunks: most relevant memory chunks for the entity
Read-only. Composes with store for multi-store scoping.
Examples: {"query": "authentication design"} {"query": "python", "max_entities": 5, "chunks_per_entity": 2} {"query": "database", "tags": ["reference"], "min_score": 0.3}
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": "memory_explore"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Restrict candidate retrieval to memories with any of these tags | |
| query | Yes | Search query used to discover candidate entities | |
| store | No | Optional store/namespace to scope retrieval (composes with multi-store support) | |
| scoring | No | Opt-in ranking mode (#55). 'composite' re-ranks chunks by semantic relevance + graph proximity + entity centrality, adding composite_score and score_components fields. Omit for default relevance-only ranking. | |
| min_score | No | Minimum relevance score for candidate chunks | |
| max_entities | No | Maximum number of entities to return | |
| chunks_per_entity | No | Maximum top chunks to include per entity |