Skip to main content
Glama

memory_clusters

Identify groups of related memories by similarity to organize and analyze connections within stored data.

Instructions

Detect clusters of related memories.

Args: min_cluster_size: Minimum memories to form a cluster (default: 2) min_score: Minimum similarity score to consider connected (default: 0.3) algorithm: "connected_components" (default) or "louvain" Louvain uses embedding similarity for content-based clustering.

Returns: List of clusters with member IDs, sizes, and common tags

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
min_cluster_sizeNo
min_scoreNo
algorithmNoconnected_components

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool implementation for 'memory_clusters' which uses _detect_clusters.
    async def memory_clusters(
        min_cluster_size: int = 2,
        min_score: float = 0.3,
        algorithm: str = "connected_components",
    ) -> Dict[str, Any]:
        """Detect clusters of related memories.
    
        Args:
            min_cluster_size: Minimum memories to form a cluster (default: 2)
            min_score: Minimum similarity score to consider connected (default: 0.3)
            algorithm: "connected_components" (default) or "louvain"
                       Louvain uses embedding similarity for content-based clustering.
    
        Returns:
            List of clusters with member IDs, sizes, and common tags
        """
        clusters = _detect_clusters(min_cluster_size, min_score, algorithm)
        return {
            "count": len(clusters),
            "clusters": clusters,
        }
  • The _detect_clusters helper function that wraps the detect_clusters storage call.
    def _detect_clusters(conn, min_cluster_size: int, min_score: float, algorithm: str = "connected_components"):
        return detect_clusters(conn, min_cluster_size, min_score, algorithm)
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses return structure ('List of clusters with member IDs, sizes, and common tags') and algorithm differences, but omits safety profile (read-only vs destructive), performance characteristics, or scope of memory scan.

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?

Uses structured docstring format with clear Args/Returns sections. Front-loaded purpose statement followed by compact parameter documentation. No redundant or filler text; every line conveys essential semantic or syntactic information.

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 3 optional parameters fully documented and an output schema present (reducing burden to describe return values), the description covers necessary ground. Minor gap: lacks explicit read-only assurance or performance notes expected for a computation-heavy clustering operation with no annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage (only titles/types). Description fully compensates by documenting all three parameters: min_cluster_size defines the threshold for cluster formation, min_score explains the similarity connection threshold, and algorithm details the two valid options with behavioral context for Louvain.

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?

Opens with specific verb-noun pair 'Detect clusters of related memories' that clearly distinguishes this grouping operation from sibling search/retrieval tools like memory_semantic_search or memory_related. Unambiguous scope.

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

Usage Guidelines3/5

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

Implies usage by explaining that Louvain 'uses embedding similarity for content-based clustering,' but provides no explicit guidance on when to choose connected_components vs louvain, or when to use clustering versus searching or listing memories.

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/agentic-box/memora'

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