Skip to main content
Glama

memory_explore

Read-only

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

NameRequiredDescriptionDefault
tagsNoRestrict candidate retrieval to memories with any of these tags
queryYesSearch query used to discover candidate entities
storeNoOptional store/namespace to scope retrieval (composes with multi-store support)
scoringNoOpt-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_scoreNoMinimum relevance score for candidate chunks
max_entitiesNoMaximum number of entities to return
chunks_per_entityNoMaximum top chunks to include per entity

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.7/5.0
Behavior5/5

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

Beyond readOnlyHint=true, the description discloses the critical behavior that it returns an empty entity list unless the graph is populated, plus backend unavailability and how to populate the graph. It also documents the return shape (entity_id, name, summary, relation_count, top_chunks) and notes that summaries are extractive and LLM-free.

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 front-loaded with purpose and prerequisites, then organized into USE THIS WHEN, return fields, and examples. Despite its length, each section serves a distinct need for a complex tool with mandatory prerequisites.

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, seven parameters, no output schema, and hard dependency on a populated graph, the definition is complete. It covers prerequisites, empty-result behavior, backend limitations, return fields, composition with store, and examples.

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 schema already documents all seven parameters and the enum. The description adds useful examples showing parameter combinations and notes store scoping, but it does not materially explain parameter meanings beyond what the schema 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?

The description gives a specific verb/resource: exploring a knowledge map of entities with query-scoped chunks per entity. It explicitly contrasts this with raw memory chunk retrieval and names sibling tools (memory_graph, memory_quality) for prerequisites, so an agent can distinguish its role.

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

Usage Guidelines5/5

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

Usage guidance is explicit: it states the graph must be populated, how to check it with memory_graph, how to populate it with memory_quality, and that it is unavailable on Cloudflare. The USE THIS WHEN bullets clearly route overview/entity-graph use cases here rather than to raw chunk search.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.