Skip to main content
Glama

cuba_zafra

Perform memory maintenance on a long-term knowledge graph by decaying, pruning, merging, summarizing, and re-encoding observations to maintain relevance and reduce redundancy.

Instructions

Memory maintenance: decay (stratified exponential by type), prune (remove low-importance), merge (deduplicate), summarize (compress observations), pagerank (personalized importance), find_duplicates, export, stats, reembed (re-encode with current model).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cNoPower-law c parameter for decay_episodes (default 0.1)
betaNoPower-law β exponent for decay_episodes (default 0.5)
actionYesConsolidation action. decay_episodes applies power-law decay to brain_episodes.
thresholdNoImportance threshold for prune (default 0.1)
batch_sizeNoMax observations to re-encode in reembed (default 500)
entity_nameNoEntity to summarize (for summarize action)
halflife_daysNoGlobal halflife override for decay (overrides per-type stratification)
compressed_summaryNoCompressed text replacing observations (for summarize)
similarity_thresholdNoSimilarity threshold for merge (default 0.8)
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only offers brief parenthetical hints (e.g., 'stratified exponential by type') but does not explain side effects, required permissions, or irreversible actions like prune or merge.

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 very concise, using a single sentence with parenthetical clarifications. However, the structure is a flat list, which reduces readability and may omit important contextual details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 9 parameters and no output schema, the description is incomplete. It fails to explain return values, error conditions, or how the tool integrates with the broader system, leaving significant gaps for an AI agent.

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 baseline is 3. The description adds no extra meaning beyond the schema; it merely lists actions without detailing how parameters like 'halflife_days' or 'similarity_threshold' affect behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Memory maintenance' and lists actions, providing a general purpose. However, it does not clearly distinguish this tool from similar sibling tools like cuba_forget or cuba_reflexion, and the list format lacks a clear verb+resource structure.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description does not mention use cases, prerequisites, or conditions under which specific actions (e.g., decay vs. prune) are appropriate.

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/LeandroPG19/cuba-memorys'

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