Skip to main content
Glama

housekeep

Clean up memory by deduplicating entries, pruning decayed patterns, removing orphan data, and rebuilding full-text search index to maintain optimal performance.

Instructions

Run cleanup, deduplication, decay, orphan cleanup, and FTS rebuild.

    Use this when you want to "clean up", "housekeep", "prune stale
    patterns", or "rebuild search" after many observations or imports.
    This is the natural-language alias for gc(); both tools are identical
    and safe to run periodically.

    Args:
        dedup_threshold: Similarity cutoff for duplicate merging,
            0.0-1.0. Default 0.75. See find_duplicates() for tuning notes.

    Returns:
        Dict with keys: "decay" (dict with "decayed" and "deleted"),
        "dedup" (dict with "found" and "applied"), "orphans_cleaned"
        (int), "fts_rebuilt" (bool).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dedup_thresholdNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description reasonably discloses behavior by listing operations and return value structure. It states it's 'safe to run periodically,' but could mention potential irreversible effects more explicitly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, with a clear bullet list of operations, usage note, and parameter description. Front-loaded main purpose. Could be slightly more streamlined but effective.

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?

Given the tool's complexity (multiple operations) and existence of output schema (return keys listed), the description is fairly complete. However, it omits potential preconditions or asynchronous behavior.

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?

Despite 0% schema coverage, the description fully explains the single parameter 'dedup_threshold': range (0.0-1.0), default (0.75), and reference to find_duplicates() for tuning, adding significant meaning beyond the schema.

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 clearly states the tool's purpose with specific verbs and resources: 'Run cleanup, deduplication, decay, orphan cleanup, and FTS rebuild.' It also distinguishes itself from the sibling 'gc' by noting they are identical.

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?

Explicitly tells when to use: 'Use this when you want to clean up, housekeep, prune stale patterns, or rebuild search after many observations or imports.' Also notes it's safe to run periodically and is an alias for gc.

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/WRG-11/instinct'

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