Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metis · Memory Curator — Consolidate Old Memories

consolidate_old_memories

Compress outdated memories into monthly summaries and archive originals to keep recall() fast while preserving knowledge. Preview changes with dry_run before consolidating.

Instructions

Consolidate old memories into monthly summaries and archive originals.

Tiered retention keeps recall() fast by compressing old raw entries into
distilled summaries while preserving the knowledge:

1. **Episodic decisions** older than decision_age_days (default 90) are
   grouped by month and project, summarised into a single consolidated
   entry per group, and the originals are marked archived=1 (excluded
   from default recall but still queryable).

2. **Session summaries** older than session_age_days (default 180) are
   marked archived=1 so they don't clutter keyword search.

3. **Reflexions** are consolidated monthly — patterns are distilled
   into a single "what we learned in month X" entry.

Run with dry_run=True first to see what would happen without changes.

Args:
    decision_age_days: Archive episodic decisions older than this (default 90).
    session_age_days: Archive session summaries older than this (default 180).
    dry_run: If True, report what would be done without making changes.

Returns:
    A report of consolidation actions taken (or planned if dry_run).

Input Schema

NameRequiredDescriptionDefault
dry_runNo
session_age_daysNo
decision_age_daysNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A5/5.0
Behavior5/5

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

Despite no annotations, the description fully discloses behavior: how decisions are grouped and summarized, session summaries archived, reflexions consolidated monthly. It clarifies that originals are marked archived but still queryable, and that recall is kept fast. No contradictions with annotations (none provided).

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?

Well-structured with bullet points and separate sections. Efficiently communicates three consolidation rules and parameter details without unnecessary words. Every sentence adds value.

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?

Complete coverage: explains what the tool does, how it works for each memory type, parameter details, and return value (a report of actions). No gaps given the tool's complexity and parameter count.

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 coverage is 0%, but the description compensates fully by explaining each parameter's purpose and default values in the Args section. dry_run is clearly described as a preview mode, decision_age_days and session_age_days have clear functions.

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 specifically states it consolidates old memories into monthly summaries and archives originals, with clear breakdown of three memory types. It distinguishes from sibling tools like consolidate_reflexions and consolidate_session_memory by being the comprehensive consolidation tool for all old memories.

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 advises to run with dry_run=True first to preview changes. Also provides default age thresholds and explains the tiered retention behavior, giving clear guidance on when to use this tool for memory maintenance.

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

Deploy Server

Other Tools