Skip to main content
Glama

gc

Run all store-maintenance tasks in one call: decay, dedup, orphans, and FTS rebuild. Combines four housekeeping steps safe and idempotent.

Instructions

Run all store-maintenance tasks in one call: decay, dedup, orphans, FTS.

    Combines four housekeeping steps:
      1. Decay confidence on patterns idle beyond the staleness threshold.
      2. Merge near-duplicates using the given similarity threshold.
      3. Remove alias entries whose target no longer exists.
      4. Rebuild the SQLite FTS index for accurate search results.

    Safe and idempotent — running more than once per day is fine. For
    finer control, the individual steps are available as find_duplicates()
    + alias_pattern() + (internal) decay.

    Args:
        dedup_threshold: Similarity cutoff for step 2, 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).

        Prefer housekeep() for discoverability; gc() remains supported for
        existing clients.
    

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?

Despite no annotations, the description explains each step and asserts safety and idempotence. It discloses that it removes orphan aliases and rebuilds FTS, covering key behaviors without contradictions.

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 well-structured with a summary, bullet steps, safety note, parameter explanation, and return format. It is front-loaded and each sentence is useful, though slightly verbose.

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 an output schema present and only one parameter, the description covers return dict keys and parameter semantics. It also provides context on housekeeping and tool discoverability, making it complete for the tool's complexity.

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

Parameters4/5

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

Schema coverage is 0%, but the description fully explains the single parameter dedup_threshold, including range, default, and reference to find_duplicates() for tuning notes, adding significant value 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 identifies the tool's purpose: running all store-maintenance tasks in one call. It enumerates the four specific steps (decay, dedup, orphans, FTS) and distinguishes it from siblings like find_duplicates() and alias_pattern().

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 states the tool is safe and idempotent, and notes that finer control is available via individual tools. Also recommends housekeep() for discoverability, providing clear guidance on when to use this tool versus alternatives.

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